Selecting, ranking, and/or presenting microsite content

ABSTRACT

A server device is configured to receive criteria that indicate when a microsite is to be provided to a user device. The user device is configured to obtain sensor data and user profile data and send the sensor data and the user profile data to the server device. The server device is configured to receive the sensor data and the user profile data, identify a relevant microsite, and provide information regarding the relevant microsite to the user device. In some cases, the service device is configured to identify that a particular microsite has been purchased by a user of the user device and provide information, to the user device, identifying that the particular microsite has been purchased.

BACKGROUND

Many techniques are available to users today to find information on theWorld Wide Web (“web”). For example, users often use web browsers and/orsearch engines to find information of interest.

Another way that users can obtain information is via push services. Pushservices are often based on information preferences expressed inadvance. For example, a user might subscribe to various informationchannels. Whenever new content is available on one of those informationchannels, a server pushes that information to the user.

SUMMARY

According to some possible implementations, a method may includereceiving, by at least one of one or more server devices, a networkaddress for a microsite; providing, by at least one of the one or moreserver devices and after receiving the network address for themicrosite, an interface that allows a user to specify criteria thatindicate when microsites are to be provided to user devices; receiving,by at least one of the one or more server devices and via the interface,criteria for the microsite, where the received criteria may specify whenthe microsite is to be provided to the user devices for rendering;associating, by at least one of the one or more server devices, thenetwork address with the received criteria; receiving, by at least oneof the one or more server devices, sensor data from a user device;determining, by at least one of the one or more server devices, that thesensor data satisfies the received criteria; and providing, by at leastone of the one or more server devices and to the user device, thenetwork address based on determining that the sensor data satisfies thereceived criteria. Providing the network address may permit the userdevice to obtain the microsite using the network address.

In some possible implementations, the interface may include a list ofcategories of criteria. Receiving the criteria for the microsite mayinclude receiving selection of the criteria from the list of categoriesof criteria.

In some possible implementations, the list of categories of criteria mayinclude one or more of a category relating to a speed at which a userdevice is moving, a category relating to a geographical location of auser device, a category relating to a manner in which a user device isbeing moved, a category relating to time or a time range, a categoryrelating to a date or a date range, a category relating to a mode oftransportation associated with a movement of a user device, a categoryrelating to a sound detected by a user device, a category relating to anevent relating to a user device, a category relating to detection of adevice within a distance of a user device, or a category relating to aperson within a distance of a user device.

In some possible implementations, the interface may include a first areaand a second area, where the first area includes the list of categoriesof criteria, and the second area includes an area that is populated witha criterion based on a selection of a category, in the list ofcategories of criteria.

In some possible implementations, receiving the first criteria mayinclude receiving, via the interface, information for combining a firstcriterion and a second criterion, using a Boolean operator, to form thecriteria for the microsite.

In some possible implementations, associating the network address withthe received criteria may include associating the network address withthe received criteria in an index. Determining that the sensor datasatisfies the received criteria may include determining that the sensordata satisfies the received criteria using the index.

In some possible implementations, the user device includes a watch.

In some possible implementations, a system may include one or moreserver devices to receive information identifying a microsite; provide,after receiving the information identifying the microsite, an interfacethat is configured to receive criteria that dictate when microsites areto be provided to user devices; receive, via the interface, particularcriteria for the microsite, where the particular criteria may specifywhen the microsite is to be provided to the user devices; associate, ina memory, the information identifying the microsite with the particularcriteria; receive sensor data from a user device; determine that thesensor data satisfies the particular criteria; and provide, to the userdevice and based on determining that the sensor data satisfies theparticular criteria, information that facilitate rendering of themicrosite by the user device.

In some possible implementations, the interface may include a list ofcategories of criteria to be used in connection with the microsites.

In some possible implementations, the list of categories of criteria mayinclude one or more of a category relating to a speed at which a userdevice is moving, a category relating to a geographical location of auser device, a category relating to a manner in which a user device isbeing moved, a category relating to time or a time range, a categoryrelating to a date or a date range, a category relating to a mode oftransportation associated with a movement of a user device, a categoryrelating to a sound detected by a user device, a category relating to anevent relating to a user device, a category relating to detection of adevice within a distance of a user device, or a category relating to aperson within a distance of a user device.

In some possible implementations, the interface may include a first areaand a second area, where the first area may include the list ofcategories of criteria, and the second area may include an area that ispopulated based on a selection of a category, in the list of categoriesof criteria.

In some possible implementations, when receiving the particularcriteria, at least one of the one or more server devices may receive,via the interface, information for combining a first criterion and asecond criterion, using a Boolean operator, to form the particularcriteria.

In some possible implementations, when associating the informationidentifying the microsite, with the particular criteria, at least one ofthe one or more server devices may associate the information identifyingthe microsite with the particular criteria in an index. When determiningthat the sensor data satisfies the particular criteria, at least one ofthe one or more server devices may determine that the sensor datasatisfies the particular criteria using the index.

In some possible implementations, the user device includes a watch.

In some possible implementations, a non-transitory computer-readablemedium for storing instructions. The instructions may include a group ofinstructions, which, when executed by one or more processors, cause theone or more processors to receive information identifying a microsite;provide, after receiving the information identifying the microsite, aninterface that is configured to receive criteria that dictate whenmicrosites are to be provided to user devices; receive, via theinterface, particular criteria for the microsite, where the particularcriteria may specify when the microsite is to be provided to the userdevices; associate, in an index, the information identifying themicrosite with the particular criteria; receive sensor data from a userdevice; and compare the sensor data and the particular criteria todetermine whether to provide the information identifying the micrositeto the user device.

In some possible implementations, the interface may include a list ofcategories of criteria to be used in connection with the microsites.

In some possible implementations, the list of categories of criteria mayinclude one or more of a category relating to a speed at which a userdevice is moving, a category relating to a geographical location of auser device, a category relating to a manner in which a user device isbeing moved, a category relating to time or a time range, a categoryrelating to a date or a date range, a category relating to a mode oftransportation associated with a movement of a user device, a categoryrelating to a sound detected by a user device, a category relating to anevent relating to a user device, a category relating to detection of adevice within a distance of a user device, or a category relating to aperson within a distance of a user device.

In some possible implementations, the interface may include a first areaand a second area, where the first area may include the list ofcategories of criteria, and the second area may include an area that ispopulated based on a selection of a category, in the list of categoriesof criteria.

In some possible implementations, one or more instructions, of the groupof instructions, to receive the particular criteria may include one ormore instructions to receive, via the interface, information forcombining a first criterion and a second criterion, using a Booleanoperator, to form the particular criteria.

In some possible implementations, the user device includes a watch.

According to some possible implementations, a method may includereceiving first sensor data associated with a user device; receivinguser profile data associated with a user of the user device; sending,independent of input of the user of the user device, the first sensordata and the user profile data to a ranking system; receiving, from theranking system, information regarding a list of microsites identifiedbased on the first sensor data or the user profile data; sending, to aserver, a request for a microsite in the list of microsites, the requestincluding second sensor data; receiving, from the server, contentassociated with the microsite, the content being based on the secondsensor data; and presenting the content for display on the user device.

According to some possible implementations, sending the first sensordata and the user profile data, receiving the information regarding thelist of microsites, sending the request for the microsite, receiving thecontent associated with the microsite, and presenting the content fordisplay may all be performed independent of input of the user of theuser device.

According to some possible implementations, sending the first sensordata and the user profile data, receiving the information regarding thelist of microsites, sending the request for the microsite, receiving thecontent associated with the microsite, and presenting the content fordisplay may all be performed without receiving a request for themicrosite from the user of the user device.

According to some possible implementations, the user device is a watch,and where presenting the content for display may include providing thecontent on a display associated with the watch.

According to some possible implementations, the information regardingthe list of microsites may include, for the microsite in the list ofmicrosites, a network address of the microsite and a list of sensorsrelevant to the microsite, and where the method may further includedetermining the second sensor data based on the list of sensors.

According to some possible implementations, sending the request for themicrosite may include using the network address to obtain the content,associated with the microsite, from the server.

According to some possible implementations, presenting the content fordisplay may include pushing the content to a display associated with theuser device so as to override any content already on the display.

According to some possible implementations, presenting the content fordisplay may include determining an appropriate time to provide thecontent for display, and presenting the content for display at theappropriate time.

According to some possible implementations, a system may include one ormore user devices to obtain first sensor data associated with the one ormore user devices; receive user profile data associated with a user ofthe one or more user devices; send, independent of input of the user ofthe one or more user devices, the first sensor data and the user profiledata to a ranking system; receive, from the ranking system, informationregarding a list of microsites identified based on at least one of thefirst sensor data or the user profile data; send, to a server, a requestfor a microsite in the list of microsites, the request including secondsensor data; receive, from the server, content associated with themicrosite, the content being based on the second sensor data; andpresent the content for display on one of the one or more user devices.

According to some possible implementations, the one or more user devicesmay send the first sensor data and the user profile data, receive theinformation regarding the list of microsites, send the request for themicrosite, receive the content associated with the microsite, andpresent the content for display independent of input of the user of theone or more user devices.

According to some possible implementations, the one or more user devicesmay send the first sensor data and the user profile data, receive theinformation regarding the list of microsites, send the request for themicrosite, receive the content associated with the microsite, andpresent the content for display without receiving a request for themicrosite from the user of the one or more user devices.

According to some possible implementations, one of the one or more userdevices is a watch, and where the watch may provide the content on adisplay associated with the watch.

According to some possible implementations, the information regardingthe list of microsites may include, for the microsite in the list ofmicrosites, a network address of the microsite and a list of sensorsrelevant to the microsite, where at least one of the one or more userdevices may determine the second sensor data based on the list ofsensors, and where at least one of the one or more user devices, whensending the request for the microsite, may use the network address toobtain the content, associated with microsite, from the server.

According to some possible implementations, at least one of the one ormore user devices, when presenting the content for display, may push thecontent to a display associated with the one of the one or more userdevices so as to override any content already on the display.

According to some possible implementations, the one or more user devicesmay include a watch and a smart phone.

According to some possible implementations, a computer-readable mediummay include a group of instructions which, when executed by one or moreprocessors of a user device, may cause the one or more processors toobtain first sensor data associated with the user device; store userprofile data associated with a user of the user device; send the firstsensor data and the user profile data to a ranking system; receive, fromthe ranking system, information regarding a list of micrositesidentified based on the first sensor data and the user profile data,where the information regarding the list of microsites may include, foreach microsite in the list of microsites, a network address for themicrosite and a list of sensors relevant to the microsite; determine,based on the list of sensors, second sensor data; send, to a server, arequest for a particular microsite in the list of microsites, where therequest may include the network address for the particular microsite andthe second sensor data; receive, from the server, content associatedwith the particular microsite, where the content may be based on thesecond sensor data; and present the content for display on the userdevice.

According to some possible implementations, instructions, of the groupof instructions which cause the one or more processors to send the firstsensor data and the user profile data, receive the information regardingthe list of microsites, determine the second sensor data, send therequest for the particular microsite, receive the content associatedwith the particular microsite, and present the content for display, mayall be executed independent of input of the user of the user device.

According to some possible implementations, instructions, of the groupof instructions which cause the one or more processors to send the firstsensor data and the user profile data, receive the information regardingthe list of microsites, determine the second sensor data, send therequest for the particular microsite, receive the content associatedwith the particular microsite, and present the content for display, mayall be executed without receiving a request for the microsite from theuser of the user device.

According to some possible implementations, one or more instructions, ofthe group of instructions, to cause the one or more processors topresent the content for display may include one or more instructions topush the content to a display associated with the user device so as tooverride any content already on the display.

According to some possible implementations, the user device is a watch,and where one or more instructions, of the group of instructions, tocause the one or more processors to present the content for display mayinclude one or more instructions to push the content to a displayassociated with the watch.

According to some possible implementations, a method may include storinginformation regarding a group of microsites, where the information mayinclude triggering criteria, for each microsite of the group ofmicrosites, that indicate when the microsite is relevant; receiving,from a user device, sensor data and user profile data, where the sensordata may be associated with the user device, and the user profile datamay be associated with the user device or a user of the user device;identifying a relevant microsite, from the group of microsites, based onthe triggering criteria and at least one of the sensor data or the userprofile data; generating a score for the relevant microsite based on amatching of the at least one of the sensor data or the user profile datato the triggering criteria; and calculating a total score based on thescore and user activity data or friend activity data, where the useractivity data may relate to user activity of the user relative to therelevant microsite, and the friend activity data may relate to useractivity of one or more social contacts, associated with the user,relative to the relevant microsite. The method may also includedetermining, based on the total score, that microsite information,associated with the relevant microsite, is to be provided to the userdevice; and providing, based on the determination, the micrositeinformation to the user device.

According to some possible implementations, the information regardingthe group of microsites may include, for the relevant microsite, anetwork address associated with the relevant microsite, the triggeringcriteria for the relevant microsite, and a list of sensors applicable tothe relevant microsite, and where providing the microsite information tothe user device may include outputting, to the user device, the networkaddress associated with the relevant microsite and the list of sensorsapplicable to the relevant microsite, where the user device may use thenetwork address and the list of sensors to obtain content for therelevant microsite.

According to some possible implementations, identifying the relevantmicrosite may include matching the sensor data or the user profile datato the triggering criteria for the group of microsites to identify agroup of relevant microsites from the group of microsites, the group ofrelevant microsites including the relevant microsite.

According to some possible implementations, the method may furtherinclude determining popularity data relating to a measure of popularity,of the relevant microsite, for a group of users, and where calculatingthe total score may include generating the total score based on thescore, the popularity data, and at least one of the user activity dataor the friend activity data.

According to some possible implementations, the friend activity data mayinclude a first type of friend activity data and a second type of friendactivity data, and where the method may further include calculating afirst score for the first type of friend activity data; calculating asecond score for the second type of friend activity data; andcalculating a third score based on the first score and the second score,and where calculating the total score may include generating the totalscore based on the score and the third score.

According to some possible implementations, receiving the sensor dataand the user profile data, identifying the relevant microsite,generating the score for the relevant microsite, calculating the totalscore, determining that the microsite information is to be provided tothe user device, and providing the microsite information may all beperformed independent of input of the user.

According to some possible implementations, determining that themicrosite information is to be provided to the user device includesdetermining that the total score, for the relevant microsite, satisfiesa threshold, and determining, based on determining that the total scoresatisfies the threshold, that the microsite information is to beprovided to the user device.

According to some possible implementations, a computer-readable mediummay include a group of instructions which, when executed by one or moreprocessors, cause the one or more processors to store informationregarding a group of microsites, where the information may includetriggering criteria, for each microsite of the group of microsites, thatindicate when the microsite is relevant; receive, from a user device,sensor data and user profile data, where the sensor data may beassociated with the user device, and the user profile data may beassociated with the user device or a user of the user device; identify arelevant microsite, from the group of microsites, based on thetriggering criteria and at least one of the sensor data or the userprofile data; generate a score for the relevant microsite based on amatching of the at least one of the sensor data or the user profile datato the triggering criteria; calculate a total score based on the scoreand popularity data, user activity data, or friend activity data, wherethe popularity data may relate to a measure of popularity of therelevant microsite, the user activity data may relate to user activityof the user relative to the relevant microsite, and the friend activitydata may relate to user activity of one or more social contacts,associated with the user, relative to the relevant microsite; determine,based on the total score, that microsite information, associated withthe relevant microsite, is to be provided to the user device; andprovide, based on the determination, the microsite information to theuser device.

According to some possible implementations, the information regardingthe group of microsites may include, for the relevant microsite, anetwork address associated with the relevant microsite, the triggeringcriteria for the relevant microsite, and a list of sensors applicable tothe relevant microsite, and where one or more instructions, of the groupof instructions, to provide the microsite information to the user devicemay include one or more instructions to output, to the user device, thenetwork address associated with the relevant microsite and the list ofsensors applicable to the relevant microsite, where the user device mayuse the network address and the list of sensors to obtain content forthe relevant microsite.

According to some possible implementations, the triggering criteria, forthe relevant microsite, may be represented as a Boolean expressionincluding a first criterion and a second criterion, and where one ormore instructions, of the group of instructions, to identify therelevant microsite may include one or more instructions to match thesensor data or the user profile data to the Boolean expression,including the first criterion and the second criterion, to determinethat the triggering criteria is satisfied.

According to some possible implementations, one or more instructions, ofthe group of instructions, to calculate the total score may include oneor more instructions to generate the total score based on the score, theuser activity data, and the friend activity data.

According to some possible implementations, the user activity data mayinclude a first type of user activity data and a second type of useractivity data, where the group of instructions may further include oneor more instructions to calculate a first score for the first type ofuser activity data; one or more instructions to calculate a second scorefor the second type of user activity data; and one or more instructionsto calculate a third score based on the first score and the secondscore, and where one or more instructions, of the group of instructions,to calculate the total score may include one or more instructions togenerate the total score based on the score and the third score.

According to some possible implementations, the group of instructionsare executed by the one or more processors without receiving a requestfor the relevant microsite from the user.

According to some possible implementations, the triggering criteria, forthe relevant microsite, may include a first criterion and a secondcriterion, and where one or more instructions, of the group ofinstructions, to generate the score for the relevant microsite mayinclude one or more instructions to calculate a first score for thefirst criterion, one or more instructions to calculate a second scorefor the second criterion, and one or more instructions to calculate thescore based on the first score and the second score.

According to some possible implementations, a system may include one ormore server devices to store information regarding a group ofmicrosites, where the information may include triggering criteria, foreach microsite of the group of microsites, that indicate when themicrosite is relevant; receive, from a user device, sensor data and userprofile data, where the sensor data may be associated with the userdevice, and the user profile data may be associated with the user deviceor a user of the user device; identify a relevant microsite, from thegroup of microsites, based on the triggering criteria and at least oneof the sensor data or the user profile data; generate a score for therelevant microsite based on a matching of the at least one of the sensordata or the user profile data to the triggering criteria; calculate atotal score based on the score, user activity data, and friend activitydata, where the user activity data may relate to user activity of theuser relative to the relevant microsite, and the friend activity datamay relate to user activity of one or more social contacts, associatedwith the user, relative to the relevant microsite; determine, based onthe total score, that microsite information, associated with therelevant microsite, is to be provided to the user device; and provide,based on the determination, the microsite information to the userdevice.

According to some possible implementations, the information regardingthe group of microsites may include, for the relevant microsite, anetwork address associated with the relevant microsite, the triggeringcriteria for the relevant microsite, and a list of sensors applicable tothe relevant microsite, and where, when providing the micrositeinformation to the user device, at least one of the one or more serverdevices may output, to the user device, the network address associatedwith the relevant microsite and the list of sensors applicable to therelevant microsite, where the user device may use the network addressand the list of sensors to obtain content for the relevant microsite.

According to some possible implementations, the triggering criteria, forthe relevant microsite, may be represented as a Boolean expressionincluding a first criterion and a second criterion, and where, whenidentifying the relevant microsite, at least one of the one or moreserver devices may match the sensor data or the user profile data to theBoolean expression, including the first criterion and the secondcriterion, to determine that the triggering criteria is satisfied.

According to some possible implementations, the one or more serverdevices may determine popularity data relating to a measure ofpopularity, of the relevant microsite, for a group of users, and where,when calculating the total score, at least one of the one or more serverdevices may generate the total score based on the score, the popularitydata, the user activity data, and the friend activity data.

According to some possible implementations, when determining that themicrosite information is to be provided to the user device, at least oneof the one or more server devices may determine that the total score,for the relevant microsite, satisfies a threshold, and determine, basedon determining that the total score satisfies the threshold, that themicrosite information is to be provided to the user device.

According to some possible implementations, the triggering criteria, forthe relevant microsite, may include a first criterion and a secondcriterion, and where, when generating the score for the relevantmicrosite, at least one of the one or more server devices may calculatea first score for the first criterion, calculate a second score for thesecond criterion, and calculate the score based on the first score andthe second score.

According to some possible implementations, a method may includereceiving, by at least one of one or more server devices, sensor datafrom a user device; identifying, by at least one of the one or moreserver devices and based on the received sensor data, a group ofmicrosites; determining, by at least one of the one or more serverdevices, that a particular microsite, in the group of microsites, hasbeen purchased by a user associated with the user device; and creating,by at least one of the one or more server devices, a list that includesinformation identifying the microsites in the group of microsites. Theinformation identifying the particular microsite may be located, withinthe list, at a location other than a top of the list. The method mayfurther include modifying, by at least one of the one or more serverdevices and based on the determining, the list, to create a modifiedlist, by moving the information identifying the particular microsite tothe top of the list; and providing, by at least one of the one or moreserver devices, to the user device, and from the modified list, theinformation identifying the particular microsite that has beenpurchased. The information identifying the particular microsite maypermit the user device to obtain a content of the particular micrositethat has been purchased.

According to some possible implementations, creating the list mayinclude generating a score for each microsite in the group ofmicrosites, and creating the list that includes information identifyingthe microsites in the group of microsites. The list may be sorted basedon the generated scores.

According to some possible implementations, providing the informationidentifying the particular microsite may include providing informationidentifying only the particular microsite, of the group of microsites,to the user device.

According to some possible implementations, determining that theparticular microsite has been purchased may include receiving, from theuser device, information identifying microsites that have beenpurchased, where the information identifying microsites that have beenpurchased including information identifies the particular microsite thathas been purchased; and using the received information to identify, inthe group of microsites, the particular microsite that has beenpurchased.

According to some possible implementations, determining that theparticular microsite has been purchased may include determining that twoor more microsites, in the group of microsites, have been purchased,where the two or more microsites include the particular microsite.Creating the list may include generating a score for each microsite inthe group of microsites, and creating the list that includes theinformation identifying the microsites in the group of microsites, wherethe list is sorted in an order based on the generated scores. Modifyingthe list may include moving the information identifying the two or moremicrosites to the top of the list, and sorting the informationidentifying the two more microsites in an order, at the top of the list,based on information from the user.

According to some possible implementations, determining that theparticular microsite has been purchased may include determining that twoor more microsites, in the group of microsites, have been purchased,where the two or more microsites include the particular microsite.Creating the list may include generating a score for each microsite inthe group of microsites, and creating the list that includes theinformation identifying the microsites in the group of microsites, wherethe list is sorted in an order based on the generated scores. Modifyingthe list may include moving the information identifying the two or moremicrosites to the top of the list, and sorting the informationidentifying the two more microsites in an order, at the top of the list,based on the generated scores.

According to some possible implementations, determining that theparticular microsite has been purchased may include determining that twoor more microsites, in the group of microsites, have been purchased,where the two or more microsites include the particular microsite.Creating the list may include generating a score for each microsite inthe group of microsites, and creating the list that includes theinformation identifying the microsites in the group of microsites, wherethe list is sorted in an order based on the generated scores. Modifyingthe list may include moving the information identifying the two or moremicrosites to the top of the list, and sorting the informationidentifying the two more microsites in an order, at the top of the list,based on one or more of dates on which the two or more microsites werepurchased or times at which the two or more microsites were purchased.

According to some possible implementations, the method may furtherinclude receiving, from the user device, criteria for the particularmicrosite, where the criteria, for the particular microsite, dictatewhen the particular microsite is to be provided to the user device.Identifying the group of microsites may include comparing the sensordata to the received criteria.

According to some possible implementations, a system may include one ormore server devices to receive sensor data from a user device; identify,based on the received sensor data, a group of microsites; determine thata particular microsite, in the group of microsites, has been purchasedby a user associated with the user device; create a list that includesinformation identifying the microsites in the group of microsites, wherethe information identifying the particular microsite is located, withinthe list, at a location other than a top of the list; modify, based ondetermining that the particular microsite has been purchased, the list,to form a modified list, by placing the information identifying theparticular microsite that has been purchased at the top of the list; andprovide, to the user device and from the modified list, at least theinformation identifying the particular microsite that has beenpurchased.

According to some possible implementations, when creating the list, atleast one of the one or more server devices may generate a score foreach microsite in the group of microsites, and create the list thatincludes information identifying the microsites in the group ofmicrosites, where the list is sorted based on the generated scores.

According to some possible implementations, when providing the at leastthe information identifying the particular microsite, at least one ofthe one or more server devices may provide information identifying onlythe particular microsite, of the group of microsites, to the userdevice.

According to some possible implementations, when determining that theparticular microsite has been purchased, at least one of the one or moreserver devices may receive, from the user device, informationidentifying microsites that have been purchased, where the informationidentifying microsites that have been purchased include the informationidentifying the particular microsite that has been purchased; and usethe received information to identify, in the group of microsites, theparticular microsite that has been purchased.

According to some possible implementations, when determining that theparticular microsite has been purchased, at least one of the one or moreserver devices may determine that two or more microsites, in the groupof microsites, have been purchased, where the two or more micrositesinclude the particular microsite. When creating the list, at least oneof the one or more server devices may generate a score for eachmicrosite in the group of microsites, and create the list that includesinformation identifying the microsites in the group of microsites, wherethe list is sorted in an order based on the generated scores. Whenmodifying the list, at least one of the one or more server devices maymove the information identifying the two or more microsites to the topof the list, and sort the information identifying the two moremicrosites in an order, at the top of the list, based on informationfrom the user.

According to some possible implementations, when determining that theparticular microsite has been purchased, at least one of the one or moreserver devices may determine that two or more microsites, in the groupof microsites, have been purchased, where the two or more micrositesinclude the particular microsite. When creating the list, at least oneof the one or more server devices may generate a score for eachmicrosite in the group of microsites, and create the list that includesthe information identifying the microsites in the group of microsites,where the list is sorted in an order based on the generated scores. Whenmodifying the list, at least one of the one or more server devices maymove the information identifying the two or more microsites to the topof the list, and sort the information identifying the two moremicrosites in an order, at the top of the list, based on the generatedscores.

According to some possible implementations, when determining that theparticular microsite has been purchased, at least one of the one or moreserver devices may determine that two or more microsites, in the groupof microsites, have been purchased, where the two or more micrositesinclude the particular microsite. When the creating the list, at leastone of the one or more server devices may generate a score for eachmicrosite in the group of microsites, and create the list that includesthe information identifying the microsites in the group of microsites,where the list is sorted in an order based on the generated scores. Whenmodifying the list, at least one of the one or more server devices maymove the information identifying the two or more microsites to the topof the list, and sort the information identifying the two moremicrosites in an order, at the top of the list, based on one or more ofdates on which the two or more microsites were purchased or times atwhich the two or more microsites were purchased.

According to some possible implementations, at least one of the one ormore server devices may receive, from the user device, criteria for theparticular microsite, where the received criteria dictate when theparticular microsite is to be provided to the user device. Whenidentifying the group of microsites, at least one of the one or moreserver devices may compare the sensor data to the received criteria.

According to some possible implementations, the user device includes awatch.

According to some possible implementations, a non-transitorycomputer-readable medium for storing instructions. The instructions mayinclude a group of instructions, which, when executed by one or moreprocessors, cause the one or more processors to receive sensor data froma user device; identify, based on the received sensor data, a group ofmicrosites; generate a score for each microsite in the group ofmicrosites; create a list that includes information identifying themicrosites in the group of microsites, where the list is sorted based onthe generated scores; determine that a particular microsite, in thegroup of microsites, has been purchased by a user associated with theuser device, where the information identifying the particular micrositeis not at a top of the list; move, based on determining that theparticular microsite has been purchased, the information identifying theparticular microsite to the top of the list to create a modified list;and provide, to the user device and from the modified list, theinformation identifying the particular microsite that has beenpurchased.

According to some possible implementations, where one or moreinstructions, of the group of instructions, to determine that theparticular microsite has been purchased may include one or moreinstructions to determine that two or more microsites, in the group ofmicrosites, have been purchased, where the two or more micrositesinclude the particular microsite. One or more instructions, of the groupof instructions, to move the information identifying the particularmicrosite to the top of the list may include one or more instructions tomove the information identifying the two or more microsites to the topof the list, and sort the information identifying the two moremicrosites in an order, at the top of the list, based on one ofinformation received from the user, the generated scores, dates on whichthe two or more microsites were purchased, or the times at which the twoor more microsites were purchased.

According to some possible implementations, the instructions may furtherinclude one or more instructions to receive, from the user device,criteria for the particular microsite, where the received criteriadictate when the particular microsite is to be provided to the userdevice. One or more instructions, of the group of instructions, toidentify the group of microsites may include one or more instructions tocompare the sensor data to the received criteria.

According to some possible implementations, a method, performed by dataprocessing apparatus, may include receiving a request from a userdevice; selecting, based on the request, a content segment from acollection of content segments based on one or more parametersassociated with each content segment, where the one or more parametersmay include a popularity metric indicating a frequency of the contentsegment, where a respective popularity metric may be assigned to eachcontent segment of the collection of content segments by a classifier,where the collection of content segments may be obtained from a group ofsources; obtaining local search results using the selected contentsegment as a query; selecting a search result from the obtained searchresults; and providing information about the search result to the userdevice.

According to some possible implementations, the one or more parametersmay include a timestamp of the request, identify a category associatedwith the request, or identify a geographic location of the user devicethat sent the request.

According to some possible implementations, the category may include aplaces category, a movies category, a shopping category, a healthcategory, or a weather category.

According to some possible implementations, obtaining local searchresults may include performing a search using the respective category asa search filter.

According to some possible implementations, the method may furtherinclude determining, based on selecting a content segment from acollection of content segments, that the content segment satisfies afrequency threshold, where the frequency threshold may represent howoften the content segment is queried.

According to some possible implementations, selecting the search resultmay include selecting a search result relevant to the selected contentsegment, where the search result may have a highest rank of the obtainedsearch results.

According to some possible implementations, the popularity metric may bebased on one or more parameters that indicate a number of similarcontent segments from the group of sources.

According to some possible implementations, a system may include aprocessor and a computer-readable medium coupled to the processor. Thecomputer-readable medium may have instructions stored thereon, which,when executed by the processor, cause the processor to: receive arequest from a user device; select, based on the request, a contentsegment from a collection of content segments based on one or moreparameters associated with each content segment, where the one or moreparameters may include a popularity metric indicating a frequency of thecontent segment, where a respective popularity metric may be assigned toeach content segment of the collection of content segments by aclassifier, where the collection of content segments may be obtainedfrom a group of sources; obtain local search results using the selectedcontent segment as a query; select a search result from the obtainedsearch results; and provide information about the search result to theuser device.

According to some possible implementations, the group of sources mayinclude search queries or public data feeds.

According to some possible implementations, the processor, whenobtaining the collection of content segments from the group of sources,may cluster content segments from the group of sources using aclustering mechanism, where the clustering mechanism may aggregate thecontent segments to remove content segments that are duplicates or haveless than a threshold quantity of typographical differences.

According to some possible implementations, the processor, whenobtaining the collection of content segments from the group of sources,may remove spam content from the content segments.

According to some possible implementations, the processor may be furtherconfigured to determine, based on selecting a content segment from acollection of content segments, that the content segment satisfies alocal relevance score, where the local relevance score may represent howrelevant the content segment is to local information.

According to some possible implementations, the selected search resultmay correspond to a business, and the information may identify operatinghours of the business, a geographic location of the business, reviews ofthe business, or a name of the business.

According to some possible implementations, a computer-readable mediummay have instructions stored thereon. The instructions may include a setof instructions which, when executed by one or more processors, causethe one or more processors to: receive a request from a user device;select, based on the request, a content segment from a collection ofcontent segments based on one or more parameters associated with eachcontent segment, where the one or more parameters may include apopularity metric indicating a frequency of the content segment, where arespective popularity metric may be assigned to each content segment ofthe collection of content segments by a classifier, where the collectionof content segments may be obtained from a group of sources; obtainlocal search results using the selected content segment as a query;select a search result from the obtained search results; and provideinformation about the search result to the user device.

According to some possible implementations, the one or more parametersmay include a timestamp of the request, identify a category, or identifya location of the user device that sent the request, and where one ormore instructions, of the set of instructions to obtain local searchresults, may include one or more instructions to perform a search usinga respective category as a search filter.

According to some possible implementations, one or more instructions, ofthe set of instructions, to obtain the collection of content segmentsfrom the group of sources, may include one or more instructions tocluster content segments from the group of sources using a clusteringmechanism, where the clustering mechanism may aggregate the contentsegments to remove content segments that are duplicates or have lessthan a threshold quantity of typographical differences.

According to some possible implementations, the instructions may furtherinclude one or more instructions to determine, based on selecting acontent segment from a collection of content segments, that the contentsegment satisfies a frequency threshold, where the frequency thresholdmay represent how often the content segment is queried.

According to some possible implementations, the instructions may furtherinclude one or more instructions to determine, based on selecting acontent segment from a collection of content segments, that the contentsegment satisfies a local relevance score, where the local relevancescore may represent how relevant the content segment is to localinformation.

According to some possible implementations, one or more instructions, ofthe set of instructions, to select the search result may include one ormore instructions to select a search result relevant to the selectedcontent segment, where the search result may have a highest rank of theobtained search results.

The above discussion mentions examples in which some implementations maybe implemented via one or more methods performed by one or moreprocessors of one or more devices. In some implementations, one or moresystems and/or one or more devices may be configured to perform one ormore of the acts mentioned above. In some implementations, acomputer-readable medium may include computer-executable instructionswhich, when executed by one or more processors, cause the one or moreprocessors to perform one or more of the acts mentioned above.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate one or more implementationsdescribed herein and, together with the description, explain theseimplementations. In the drawings:

FIGS. 1A, 1B, and 1C are diagrams illustrating an overview of an exampleimplementation described herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 3 is a diagram of example functional components of the rankingsystem of FIG. 2;

FIGS. 4 and 5 are flowcharts of example processes for setting criteriafor triggering when microsite content is to be presented to a userdevice;

FIGS. 6A, 6B, and 6C are diagrams of example user interfaces that allowmicrosite creators to specify triggering criteria for pushing micrositecontent;

FIG. 7 is a flowchart of an example process for providing content of amicrosite;

FIG. 8 is a diagram illustrating an overview of an exampleimplementation described herein;

FIG. 9 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 10 is a diagram of example functional components of the user deviceof FIG. 9;

FIG. 11 is a diagram of example functional components of the rankingsystem of FIG. 9;

FIG. 12 is a flowchart of an example process for presenting content of amicrosite;

FIG. 13 is a flowchart of an example process for providing informationregarding a set of microsites;

FIG. 14 is a flowchart of an example process for providing content of amicrosite;

FIG. 15 is a diagram illustrating an example process flow that involvesthe user device, the ranking system, and the servers of FIG. 9;

FIG. 16, FIG. 17A, FIG. 17B, FIG. 17C, and FIG. 17D illustrate examplesof microsite content that may be presented in certain contexts;

FIG. 18 is a diagram illustrating an overview of an exampleimplementation described herein;

FIG. 19 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 20 is a diagram of example functional components of the user deviceof FIG. 19;

FIG. 21 is a diagram of example functional components of the rankingsystem of FIG. 19;

FIG. 22 is a diagram of an example entry that may be stored in an indexmaintained by the indexing module of FIG. 21;

FIG. 23 is a diagram of example functional components of the rankingmodule of FIG. 21;

FIG. 24A, FIG. 24B, and FIG. 24C are examples of functions that may beused to generate real values based on matching sensor data and/or userprofile data to triggering criteria;

FIG. 25 is a flowchart of an example process for presenting content of amicrosite;

FIG. 26 is a flowchart of an example process for providing informationregarding a set of microsites;

FIG. 27 is a flowchart of an example process that may correspond to aportion of the process of FIG. 26;

FIG. 28 is a diagram illustrating an example process flow that involvesthe user device, the ranking system, and the servers of FIG. 19;

FIG. 29, FIG. 30, FIG. 31, FIG. 32, FIG. 33, FIG. 34, FIG. 35, and FIG.36 illustrate an example of identifying and presenting micrositecontent;

FIG. 37A, FIG. 37B, FIG. 37C, and FIG. 37D are diagrams illustrating anoverview of an example implementation described herein;

FIG. 38 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 39 is a diagram of example functional components of the user deviceof FIG. 38;

FIG. 40 is a diagram of example functional components of the rankingsystem of FIG. 38;

FIG. 41 is a flowchart of an example process relating to purchasing amicrosite;

FIG. 42, FIG. 43A, and FIG. 43B are flowcharts of example processes forproviding a microsite to a user device;

FIG. 44A, FIG. 44B, FIG. 44C, and FIG. 44D are diagrams of an example ofthe process described in FIGS. 42-43B;

FIG. 45 is a schematic diagram of an example signal based recommendersystem;

FIG. 46 is a flowchart of an example method of identifying userintentions;

FIG. 47 is a flowchart of an example method of providing a search resultto a user;

FIG. 48 is a diagram of an example device that includes an interfaceshowing information about a relevant search result; and

FIG. 49 is a diagram of an example of a generic computer device and ageneric mobile computer device.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

In the description to follow, various examples of systems and methodsrelating to the presentation of microsites will be described. Amicrosite may be broadly defined as a mini-web page that may bepresented based on a network address, such as a uniform resource locator(URL) or a uniform resource identifier (URI), associated with themicrosite. As used herein, a microsite includes an amount of contentthat can be presented in a user-discernible format on a display of awatch or in a display area the size of the display of a watch. In someimplementations, a microsite is configured to display less than 100, 50,or 20 words to a user at a time, and/or less than 1000, 500, or 300characters. In some implementations, a microsite includes content, suchas embedded instructions (e.g., Javascript), data, image information, ormetadata.

While the descriptions, herein, are described in terms of presentinginformation regarding microsites, the description may also apply topresenting documents. A document, as the term is used herein, is to bebroadly interpreted to include any machine-readable and machine-storablework product. A document may include, for example, an e-mail, a website, a microsite, a file, a combination of files, one or more fileswith embedded links to other files, a news article, a blog, a discussiongroup forum, etc. In the context of the Internet, a common document is aweb page. Web pages often include textual information and may includeembedded information, such as meta information, images, hyperlinks,etc., and/or embedded instructions, such as Javascript.

For the described systems and methods, the users can control whether theprograms or features collect user personal information (e.g.,information about a user's social network, actions, activities, a user'spreferences, or a user's current location), or the extent suchinformation is collected or used. In addition, certain data may betreated in one or more ways before the data is stored or used, so thatpersonally identifiable information is removed, encrypted, and/orotherwise protected for the user. Thus, the user may have control overhow information about the user is collected and used by a server.

While the descriptions of the examples are presented separately fromeach other, the descriptions are interchangeable and combinable invarious ways. Thus, some or all of one example may be combined with someor all of one or more other examples.

Example 1

A system and/or method, as described herein, may allow a creator of amicrosite to specify criteria that dictates when the microsite is to bepresented—e.g., pushed—to a user device. A ranking system may associatethe specified criteria with information identifying the microsite in,for example, an index. The ranking system may subsequently receivesensor data from a user device. If the sensor data matches the specifiedcriteria, the ranking system may identify the microsite as a candidatein determining which microsite content is to be presented to the userdevice. The microsite content may include information that may be usefulto the user.

FIGS. 1A-1C are diagrams illustrating an overview 100 of an exampleimplementation described herein. Assume that a microsite creator—e.g., asoftware engineer, a web developer, a designer, a group of softwareengineers, web developers, and/or designers, etc.—has designed amicrosite relating to working out. For example, the workout micrositemay provide a user, who has gone out for a run, with informationregarding the distance that the user has run, the speed at which theuser is running, and the number of calories that the user has burned. Asshown in FIG. 1A, the creator may provide information identifying theworkout microsite, such as a URL or a URI, to a ranking system. Thecreator may also specify, to the ranking system, triggering criteria,which dictate when the creator's workout microsite is to be presented toa user device. In the example of FIG. 1A, assume that the creator hasspecified three triggering criteria for presenting the workoutmicrosite: (1) that the user must be moving faster than 7 kilometers perhour (km/hr) for more than 4 minutes; (2) that the user must not bewithin 10 meters of a bus stop; and (3) that the time must not bebetween 11 PM and 4 AM.

With reference to FIG. 1B, assume that a user, named Mary, is associatedwith a user device (shown as a watch in FIG. 1B) that is capable ofreceiving microsite content. Assume that Mary's watch periodically sendssensor data to the ranking system and that the sensor data includesinformation identifying a current time, information identifying acurrent geographic location of the watch, information identifying aspeed at which the watch is currently moving (e.g., based on globalpositioning satellite (GPS) data), and/or other information. In theexample of FIG. 1B, assume that Mary's watch sends, over a first periodof time, first sensor data. Based on the first sensor data, assume thatthe ranking system determines that the current time at the geographiclocation of Mary's watch is 8:10 AM, that Mary's watch has been movingat a speed of greater than 7 km/hr for more than 4 minutes, and that thegeographic location of Mary's watch is not within 10 meters of a busstop. The ranking system may determine that the sensor data, from Mary'swatch, satisfies the triggering criteria of the workout microsite. As aresult, the ranking system may cause the workout microsite to bepresented to Mary's watch, as illustrated in FIG. 1B.

With reference to FIG. 1C, assume that Mary's watch sends, over a secondperiod of time, second sensor data. Based on the second sensor data,assume that the ranking system determines that the current time at thegeographic location of Mary's watch is 8:30 AM, and that Mary's watchhas been moving at a speed of greater than 7 km/hr for more than 4minutes. In the example of FIG. 1C, however, assume that the rankingsystem determines that the geographic location of Mary's watch is within10 meters of a bus stop. The ranking system may determine, as a resultof the geographic location of Mary's watch being within 10 meters of abus stop, that the sensor data, from Mary's watch, does not satisfy thecriteria of the workout microsite. As a result, the ranking system maynot cause the workout microsite to be presented to Mary's watch, asillustrated in FIG. 1C. In those situations where the ranking systemdoes not identify any other microsites as relevant to the second sensordata, Mary's watch may, for example, simply display a clock.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. Environment 200 mayinclude a user device 210 and a microsite creator device 220 connectedto a ranking system 230, and multiple servers 240-1 through 240-N (whereN>1) (referred to collectively as “servers 240” and, at times,individually, as “server 240”) via a network 250.

User device 210 may include a client device, or a collection of clientdevices, that is capable of presenting a document on a display. Examplesof user device 210 may include a smart phone, a personal digitalassistant, a laptop, a tablet computer, a camera, a watch, a personalcomputer, and/or another type of device with the ability to display amicrosite. In some implementations, user device 210 may include abrowser via which a microsite may be presented on a display associatedwith user device 210.

Microsite creator device 220 may include a device via which a micrositecreator may specify triggering criteria, for a microsite, that dictatewhen the microsite is to be presented, for display, on a user device210. Examples of a microsite creator device 220 may include a personalcomputer, a laptop, a tablet computer, a smart phone, a personal digitalassistant, and/or another type of device. In some implementations,microsite creator device 220 may include a browser that allows micrositecreator device 220 to access ranking system 230 to specify thetriggering criteria for a microsite.

Ranking system 230 may include a server device or a collection of serverdevices which may be co-located or remotely located. Ranking system 230may identify microsites and index information associated with themicrosites. Ranking system 230 may identify relevant microsites topresent to a user device 210, based on, for example, context informationreceived from user device 210 and triggering criteria for triggering thepresentation of the microsites, and provide information regarding therelevant microsites to user device 210. In addition, ranking system 230may provide one or more user interfaces, to microsite creator device220, to allow for specification of triggering criteria for a microsite.

Server 240 may include a server device or a collection of server devicesthat may be co-located or remotely located. Any two or more of servers240 may be implemented within a single, common server device or asingle, common collection of server devices. Servers 240 may hostdocuments, such as microsites. In some implementations, one or more ofservers 240 may be affiliated with a same entity (e.g., party,organization, business, company, etc.) as ranking system 230. In someimplementations, none of servers 240 may be affiliated with the sameentity as ranking system 230.

While ranking system 230 is shown as separate from servers 240, it maybe possible for ranking system 230 to perform one or more of thefunctions described as being performed by a server 240 and/or a server240 to perform one or more of the functions described as being performedby ranking system 230. For example, ranking system 230 may host some orall of the microsites. Additionally, or alternatively, a user device 210may host some of the microsites and/or perform one or more of thefunctions of ranking system 230.

Network 250 may include any type of network, such as, for example, alocal area network (“LAN”), a wide area network (“WAN”), a telephonenetwork, such as the Public Switched Telephone Network (“PSTN”) or acellular network, an intranet, the Internet, or a combination of theseor other types of networks. User device 210, microsite creator device220, ranking system 230, and servers 240 may connect to network 250 viawired and/or wireless connections. In other words, any one of userdevice 210, microsite creator device 220, ranking system 230, and/orservers 240 may connect to network 250 via a wired connection, awireless connection, or a combination of a wired connection and awireless connection.

Although FIG. 2 shows example components of environment 200, in someimplementations, environment 200 may include additional components,fewer components, different components, or differently arrangedcomponents than those depicted in FIG. 2. Additionally, oralternatively, one or more components of environment 200 may perform oneor more tasks described as being performed by one or more othercomponents of environment 200.

FIG. 3 is a diagram of example functional components of ranking system230. In some implementations, the functional components, shown in FIG.3, may be implemented by ranking system 230. In some implementations,one or more of the functional components, shown in FIG. 3, may beimplemented by a system or device separate from ranking system 230, suchas a user device 210 operating alone or in combination with rankingsystem 230. As shown in FIG. 3, ranking system 230 may include an inputcomponent 310, an indexing component 320, and a ranking component 330.

Input component 310 may identify microsites for use by ranking system230. In some implementations, input component 310 may identifymicrosites through crawling. For example, input component 310 mayinclude or interact with a crawler to locate microsites on a network,such as network 250. The crawler may follow links to locate documents onthe network. Input component 310 may determine which documents aremicrosites by locating particular information on documents that aremicrosites. This particular information may include a piece of code thatidentifies the document as a microsite.

In some implementations, input component 310 may identify microsites viamanual input. For example, input component 310 may provide a userinterface via which microsite creators may provide information regardingmicrosites that the microsite creators have created. In someimplementations, a microsite creator, via the user interface, mayidentify a network address, such as a URL or a URI, associated with amicrosite. Additionally, or alternatively, the microsite creator, viathe user interface, may upload the content of the microsite. The contentof the microsite may be hosted by ranking system 230 or a deviceseparate from ranking system 230, such as a server 240.

Input component 310 may also provide a user interface that allowsmicrosite creators to specify other information in relation to amicrosite. For example, the user interface may allow a microsite creatorto specify triggering criteria that dictate when the creator's micrositeis to be presented—e.g., pushed—to a user device 210. In someimplementations, the user interface may include a list of triggeringcriteria categories, such as a location category, a time category, amotion category, a transport mode category, a sound category, a datecategory, a device event category, an other devices category, a peoplecategory, a speed category, and/or other types of categories. Themicrosite creator may select from among the list of triggering criteriacategories and provide parameters for specifying the triggering criteriafor the microsite. Additionally, or alternatively, the user interfacemay allow the microsite creator to specify the triggering criteria forthe microsite in other ways.

The location category may allow the microsite creator to specifycriteria relating to a geographic location of a user device 210. As oneexample, a criterion under the location category may specify that thecriterion is satisfied when a user device 210 is or is not at aparticular geographic location. Additionally, or alternatively, acriterion under the location category may specify that the criterion issatisfied when a user device 210 is or is not within a certain distanceof a geographic location. The geographic location may be specified, forexample, as a particular geographic address, a particular set ofgeographic coordinates, a particular type of location, and/or in anothermanner. A type of location may be expressed generally, such as, forexample, a bus stop, an airport, a gas station, a restaurant, etc., ormore specifically, such as, for example, a particular type of restaurantor a particular restaurant, a particular country, state, city, or town,etc. As an example, a criterion, in the location category, may specifythat the criterion is satisfied if sensor data, from a user device 210,indicates that user device 210 is within a park. As another example, alocation criterion may specify that the criterion is satisfied if sensordata from a user device 210 indicates that user device 210 is not within10 meters of a bus stop.

The time category may allow the microsite creator to specify criteriarelating to a time or time range. As one example, a criterion under thetime category may specify that the criterion is satisfied when thecurrent time, at the geographic location of a user device 210, is or isnot at a particular time, or is or is not within a particular timerange. A time range may be expressed specifically, for example, using astart time and an end time, or more generally as, for example, day time,nighttime, morning, afternoon, evening, dinner time, lunch time, etc. Asan example, a criterion, in the time category, may specify that thecriterion is satisfied if sensor data from a user device 210 indicatesthat the current time, at the geographic location of user device 210, isnot within a time range of 11 PM and 4 AM.

The motion category may allow the microsite creator to specify criteriarelating to a motion of a user device 210. As one example, a criterionunder the motion category may specify that the criterion is satisfiedwhen user device 210 is or is not being moved in a particular motion.Examples of motions may include walking, running, driving in a car,riding on a train, etc. As an example, a criterion, in the motioncategory, may specify that the criterion is satisfied if sensor datafrom a user device 210 indicates that a user, of user device 210, isrunning.

The transport mode category may allow the microsite creator to specifycriteria relating to a transport mode being used by a user of a userdevice 210. As one example, a criterion under the transport modecategory may specify that the criterion is satisfied when user device210 is or is not currently being moved by a particular transport mode.Examples of transport modes may include a bus, a car, a ferry, a train,foot, bicycle, etc. To distinguish between these different modes oftransportation, ranking system 230 may collect sensor data relating tousers who are using these different transportation modes and determine,for example, a pattern of movement of user devices 210 that isindicative of each different type of travel. In this way, ranking system230 may distinguish when a user is moving via bus, car, ferry, train,foot, bicycle, etc. As an example, a criterion, in the transport modecategory, may specify that the criterion is satisfied if sensor datafrom a user device 210 indicates that a user, of user device 210, iscurrently walking.

The sound category may allow the microsite creator to specify criteriarelating to a sound that is currently being detected by a user device210. As one example, a criterion under the sound category may specifythat the criterion is satisfied when user device 210 is or is notcurrently detecting a particular sound. Examples of factors on which acriterion in this category may be based may include detection of a voiceor a particular type of voice (e.g., such as a male voice, a femalevoice, a child's voice, etc.), detection of a collection of voices(e.g., a crowd), detection of a particular word or words, detection ofmusic or a particular type of music, detection of a song (e.g., anysong), a particular song (e.g., a song with a specific name), or aparticular type of song (e.g., a rock and roll song), etc. Additionally,or alternatively, a criterion under the sound category may specify thatthe criterion is satisfied when user device 210 is or is not currentlydetecting sound above or below a particular threshold. As an example, acriterion, in the sound category, may specify that the criterion issatisfied if sensor data from a user device 210 indicates that userdevice 210 is currently detecting music being played.

The date category may allow the microsite creator to specify criteriarelating to a date or date range. As one example, a criterion under thedate category may specify that the criterion is satisfied when thecurrent date, at the geographic location of a user device 210, is or isnot a particular date, or is or is not within a particular date range. Adate range may be expressed specifically, for example, using a startdate and an end date, or more generally as, for example, a particularday or days, a particular week or weeks, a particular month or months,summer, fall, winter, spring, a particular holiday, etc. As an example,a criterion, in the date category, may specify that the criterion issatisfied if sensor data from a user device 210 indicates that thecurrent date, at the geographic location of user device 210, is within adate range of Jun. 1, 2012 and Jun. 30, 2012.

The device event category may allow the microsite creator to specifycriteria relating to a particular event that is currently being detectedby a user device 210. As one example, a criterion under the device eventcategory may specify that the criterion is satisfied when user device210 is or is not currently connected to a Wi-Fi network. Examples offactors on which a criterion in this category may be based may includewhether a user device 210 is or is not currently connected to network,whether user device 210 is currently connected to a particular type ofnetwork, whether a network is available to which user device 210 canconnect, whether user device 210 is currently receiving a telephonecall, whether user device 210 is currently conducting a telephone call,whether a telephone call has ended in connection with user device 210,whether a new message has arrived in a voicemail account associated withuser device 210, whether a battery level of user device is at, above, orbelow a threshold, whether user device 210 is currently charging, etc.As an example, a criterion, in the device event category, may specifythat the criterion is satisfied if sensor data from a user device 210indicates that battery of user device 210 is below a particularthreshold.

The other devices category may allow the microsite creator to specifycriteria relating to one or more devices that are currently beingdetected by a user device 210. As one example, a criterion under theother devices category may specify that the criterion is satisfied whenuser device 210 is in proximity to another user device. Examples offactors on which a criterion in this category may be based may includewhether a user device 210 is or is not within a particular distance ofanother device (e.g., a cell phone, a Wi-Fi access point, etc.), anotherparticular device (e.g., a particular's friend's cell phone), etc. As anexample, a criterion, in the other devices category, may specify thatthe criterion is satisfied if sensor data from a user device 210indicates that user device 210 is within a particular distance of aWi-Fi access point, having a particular service set identifier (SSID).

The people category may allow the microsite creator to specify criteriarelating to a person who may be in proximity to a user device 210. Asone example, a criterion under the people category may specify that thecriterion is satisfied when user device 210 is in proximity to aparticular person, which can be determined, for example, based ondetecting a user device with which the particular person is associated.Examples of factors on which criterion in this category may be basedinclude whether a user device 210 is within a particular distance of aparticular person, people with one or more characteristics in commonwith the user of user device 210, etc. To determine whether anotherperson has a characteristic in common with the user, a social networkingwebsite, an address book, or other information may be considered. As anexample, a criterion, in the people category, may specify that thecriterion is satisfied if sensor data from a user device 210 indicatesthat a person who is associated with a user, of user device 210, on asocial networking website is within proximity of user device 210.

The speed category may allow the microsite creator to specify criteriarelating to a speed at which user device 210 is currently moving. As oneexample, a criterion under the speed category may specify that thecriterion is satisfied when user device 210 is or is not moving at aparticular speed for a particular period of time. Examples of factors onwhich a criterion in this category may be based include whether userdevice 210 is or is not moving at, above, or below a particular speed,whether user device 210 is or is not moving at, above, or below aparticular speed for longer than a particular period of time, whetheruser device 210 is or is not moving at, above, or below a particularspeed for less than a particular period of time, etc. As an example, acriterion, in the speed category, may specify that the criterion issatisfied if sensor data from a user device 210 indicates that userdevice 210 is moving faster than 7 kilometers per hour for longer than 4minutes.

While specific triggering criteria categories are discussed above, theuser interface may include additional categories, fewer categories, ordifferent categories. For example, the list of triggering criteriacategories may also include an orientation category that may allow themicrosite creator to specify criteria relating to an orientation of userdevice 210. As an example, a criterion, in the orientation category, mayspecify that the criterion is satisfied if sensor data from a userdevice 210 indicates that a display of user device 210 is facing awayfrom a user of user device 210.

Each triggering criteria category may be associated with one or moresensors. Thus, input component 310 may identify, based on selection ofparticular triggering criteria categories for a particular microsite, alist of sensors that are relevant to the particular microsite. Inputcomponent 310 may provide the triggering criteria and/or the list ofsensors to indexing component 320.

Indexing component 320 may include one or more indexes that may bestored in one or more memory devices, which may be co-located orremotely located. In some implementations, indexing component 320 maystore information regarding various microsites in an index. For aparticular microsite, for example, the index may store a descriptivename of the particular microsite, a network address for the particularmicrosite, triggering criteria for the particular microsite, and/or alist of sensors that are relevant for the particular microsite. Rankingcomponent 330 may use the information in the index to identifymicrosites that are relevant for a particular user and/or in aparticular situation.

Ranking component 330 may receive sensor data from user device 210.Ranking component 330 may use the sensor data to identify relevantmicrosites. In some implementations, ranking component 330 may identifymicrosites that are relevant based on the sensor data and the triggeringcriteria, compare the sensor data to the triggering criteria for themicrosites, and generate scores for the microsites based on a result ofthe comparisons. For example, ranking component 330 may perform a firstanalysis to identify relevant microsites based on the sensor data andthe triggering criteria; and perform a second analysis on the relevantmicrosites, based on a comparison of the sensor data and the triggeringcriteria, to generate a score for each of the relevant microsites.

In some example implementations, ranking component 330 may modify thescore, of a microsite, based on one or more factors. For example,ranking component 330 may modify the score, of a microsite, based on apopularity score of the microsite. In some implementations, thepopularity score of a microsite may be generated based on user behaviordata associated with the microsite, such as how many users expresseddisinterest in the microsite by, for example, swiping away from themicrosite or providing a negative rating when the microsite waspresented to a user device 210, and/or how many users expressed interestin the microsite by, for example, providing a positive rating when themicrosite was presented to a user device 210, requesting additionalinformation regarding the microsite, or purchasing a service associatedwith the microsite. In some implementations, the popularity score of amicrosite may be generated using one or more factors instead of, or inaddition to, the user behavior data, such as a quantity of times thatthe microsite has been presented to user devices 210, an age of themicrosite, a prior ranking or score of the microsite, or the like.

Additionally, or alternatively, ranking component 330 may modify thescore, of a microsite, based on a personalization score of themicrosite. In some implementations, the personalization score of amicrosite may be generated based on user activity data, associated witha user of a particular user device 210, with regard to the microsite,such as whether the user has expressed disinterest in the microsite by,for example, swiping away from the microsite or providing a negativerating when the microsite was presented to the particular user device210, and/or whether the user expressed interest in the microsite by, forexample, providing a positive rating when the microsite was presented tothe particular user device 210, requesting additional informationregarding the microsite, purchasing a service associated with themicrosite, bookmarking the microsite, and/or following a recommendationprovided by the microsite—e.g., a recommendation to visit a particularrestaurant, see a particular movie, ride a particular bus, or the like.In some implementations, the personalization score of a microsite may begenerated using one or more factors instead of, or in addition to, theuser activity data, such as whether the user has recommended themicrosite to one of the user's social contacts.

Additionally, or alternatively, ranking component 330 may modify thescore, of a microsite, based on a social score of the microsite. In someimplementations, the social score of a microsite may be generated basedon friend activity data, associated with social contacts—e.g., socialcontacts—of the user of a particular user device 210, with regard to themicrosite. The user's social contacts may be identified based on theuser's communications, the user's address book, and/or the user'saccount on one or more social networks. Examples of friend activitydata, associated with a microsite, include whether the user's socialcontacts have expressed disinterest in the microsite by, for example,swiping away from the microsite or providing a negative rating when themicrosite was presented to the social contacts' user devices 210, and/orwhether the user's social contacts expressed interest in the micrositeby, for example, providing a positive rating when the microsite waspresented to the social contacts' user devices 210, requestingadditional information regarding the microsite, purchasing a serviceassociated with the microsite, bookmarking the microsite, and/orfollowing a recommendation provided by the microsite—e.g., arecommendation to visit a particular restaurant, see a particular movie,ride a particular bus, or the like. In some implementations, the socialscore of a microsite may be generated using one or more factors insteadof, or in addition to, the friend activity data, such as whether thesocial contacts have recommended the microsite to others.

In some implementations, ranking component 330 may generate a totalscore for a microsite based on a combination of the score and thepopularity score, the personalization score, and/or the social score. Insome implementations, ranking component 330 may generate a total scorefor a microsite based on a combination of the score, the popularityscore, the personalization score, and the social score. In someimplementations, ranking component 330 may generate a total score for amicrosite based on a weighted combination of the score, the popularityscore, the personalization score, and the social score. For example,ranking component 330 may assign a weight value to the score, thepopularity score, the personalization score, and/or the social score.The weight values may differ—in other words, the amount that each of thescore, the popularity score, the personalization score, and the socialscore contributes to the total score may vary. Rank component 330 maycombine the weighted score, the weighted popularity score, the weightedpersonalization score, and/or the weighted social score to generate thetotal score.

Ranking component 330 may select a set of microsites based on theirscores. For example, ranking component 330 may select the top scoring Xmicrosites (X>1). In some implementations, ranking component 330 mayselect only the top scoring microsite (X=1). In some implementations,ranking component 330 may select the top scoring five (5) microsites(X=5).

Ranking component 330 may provide information, regarding the set ofmicrosites, to user device 210. In some implementations, the informationmay include a network address and/or a list of sensors for eachmicrosite in the set of microsites. In some implementations, the networkaddresses of the microsites may be provided in a ranked list based onthe scores of the microsites. In some implementations, the networkaddresses of the microsites may be provided along with the scores of themicrosites.

Although FIG. 3 shows example functional components of ranking system230, in some implementations, ranking system 230 may include additionalfunctional components, different functional components, or fewerfunctional components than those depicted in FIG. 3. Additionally, oralternatively, one or more functional components of ranking system 230may perform one or more tasks described as being performed by one ormore other functional components of ranking system 230.

FIG. 4 is a flowchart of an example process 400 for setting criteria fortriggering when microsite content is to be presented—e.g., pushed—to auser device. In some implementations, process 400 may be performed byranking system 230. In some implementations, one or more blocks ofprocess 400 may be performed by one or more devices instead of, orpossibly in conjunction with, ranking system 230, such as by user device210.

Process 400 may include receiving information identifying a microsite(block 410). For example, input component 310, of ranking system 230,may provide a user interface to a microsite creator device 220. In someimplementations, the microsite creator may access the user interface,using microsite creator device 220, via a browser or in another manner.The microsite creator may provide information identifying the microsite,via the user interface. For example, the microsite creator may identifythe microsite by providing a network address, such as a URL or a URI,using the user interface. Additionally, the microsite creator mayspecify other information identifying the microsite, such as a name ofthe microsite, via the user interface. Input component 310 may receivethe network address and the other information.

Process 400 may include providing a triggering criteria interface (block420). For example, input component 310, of ranking system 230, mayprovide a user interface via which a microsite creator may specifytriggering criteria that dictate when a microsite is to bepresented—e.g., pushed—to a user device 210. In some implementations,input component 310 may provide the user interface based on receivingthe information identifying the microsite. As described above, the userinterface may include a list of triggering criteria categories, such asa location category, a time category, a motion category, a transportmode category, a sound category, a date category, a device eventcategory, an other devices category, a people category, a speedcategory, and/or other types of categories. The microsite creator mayselect from among the list of triggering criteria categories and provideparameters for specifying the triggering criteria for the microsite.

Process 400 may include receiving triggering criteria for the microsite(block 430). For example, input component 310 may receive, via the userinterface, one or more triggering criteria for the microsite. In someimplementations, the user interface may provide the microsite creatorwith the ability to specify how different triggering criteria and/ordifferent triggering criteria categories are to be combined. In someimplementations, the user interface may allow for different triggeringcriteria and/or different triggering criteria categories to be combinedusing one or more Boolean operators. For example, assume that thetriggering criteria for the microsite include criteria relating tospeed, motion, and time. The user interface may allow the threetriggering criteria to be combined in many different ways, such as, forexample:

speed AND motion AND time,

speed OR motion OR time,

(speed OR motion) AND time,

speed AND (motion OR time),

etc.

Thus, Boolean operators and/or parentheses may be used to specify howdifferent triggering criteria are to be combined for the microsite. Insome implementations, the microsite creator may also provide differentweights for the different criteria that are part of the triggeringcriteria. In the example above, the microsite creator may specify afirst weight for the speed criteria, a second, different weight for themotion criteria, and a third, different weight for the time criteria.

Additionally, or alternatively, input component 310 may provide a userinterface that allows the microsite creator to specify triggeringcriteria in other ways. For example, the user interface may allow themicrosite creator to specify triggering criteria in a freestyle manner,such as by typing in what the microsite creator desires the triggeringcriteria to be. As one example, the microsite creator may specify thetriggering criteria shown in FIG. 1A as:

-   -   the criteria is met when the user device is moving faster than 7        km/hr for longer than 4 minutes, and the user device is not        within 10 meters of a bus stop, and the time is not between 11        PM and 4 AM.

Input component 310 may receive the entered information and parse theinformation to identify the triggering criteria categories and thetriggering criteria for the identified triggering criteria categories.Additionally, or alternatively, input component 310 may provide defaulttriggering criteria, which can be edited by the microsite designer tospecify the triggering criteria for the microsite. The defaulttriggering criteria may be provided, for example, in an ExtensibleMarkup Language (XML) format, a Comma (or Character)-Separated Values(CSV) format, a Microsoft Excel (XLS) format, a non-string type offormat, and/or another type of format; as a flat text file (e.g.,ASCII); as a file containing an array of key-value pairs; etc. In someimplementations, the default triggering criteria may include an entirelist of possible criteria or a subset of possible criteria, which may bedetermined based on a type of the microsite received in block 410 above.In some implementations, the microsite creator may simply remove thetriggering criteria that are not desired and provide the appropriateparameters for the remaining triggering criteria to form the triggeringcriteria for the microsite.

Process 400 may include associating, in an index, the receivedtriggering criteria with information identifying the microsite (block440). For example, indexing component 320, of ranking system 230, mayreceive the triggering criteria from input component 310. In addition,indexing component 320 may receive information identifying themicrosite, such as a network address, from input component 310. In someimplementations, indexing component 310 may also receive a name of themicrosite and a list of sensors that are relevant to the microsite frominput component 310. Indexing component 320 may store, for a particularmicrosite and in the index, a descriptive name of the particularmicrosite, a network address for the particular microsite, triggeringcriteria for the particular microsite, and/or a list of sensors that arerelevant for the particular microsite.

While FIG. 4 shows process 400 as including a particular quantity andarrangement of blocks, in some implementations, process 400 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIG. 5 is a flowchart of example process 500 that may correspond toblocks 420 and 430 of FIG. 4. In some implementations, process 500 maybe performed by ranking system 230. In some implementations, one or moreblocks of process 500 may be performed by one or more devices insteadof, or possibly in conjunction with, ranking system 230. Process 500will be described in connection with FIGS. 6A-6C, which depict userinterfaces that may be used for specifying triggering criteria for amicrosite.

Process 500 may include providing a user interface with a list oftriggering criteria categories (block 510). For example, input component310, of ranking system 230, may provide a user interface to a micrositecreator device 220 that allows the microsite creator to specify thetriggering criteria for an identified microsite. In someimplementations, the user interface may include a list of triggeringcriteria categories, such as, for example, a location category, a timecategory, a motion category, a transport category, a sound category, adate category, a device event category, an other devices category, apeople category, a speed category, and/or other types of categories.These categories were discussed above with respect to FIG. 3.

FIG. 6A is a diagram of an example user interface 600 that may beprovided to a microsite creator in connection with block 510. As shown,user interface 600 may include a first area 610 that includes a list oftriggering criteria categories that may be used to specify triggeringcriteria for a microsite and a second area 620 that acts as a canvas forreceiving selections of triggering criteria categories.

Returning to FIG. 5, process 500 may include detecting selection of atriggering criteria category (block 520). For example, input component310 may detect that the microsite creator selected a triggering criteriacategory from the list of triggering criteria categories. With referenceto FIG. 6A, the microsite creator may select the triggering criteriacategory by dragging a triggering criteria category from first area 610to second area 620. Other manners of selecting a triggering criteriacategory may alternatively be used. For example, the microsite creatormay select a triggering criteria category by clicking on the triggeringcriteria category, in first area 610, with a mouse or other type ofinput device, or touching the triggering criteria category, in firstarea 610, with a finger or input device.

Process 500 may include populating the user interface with informationfor the selected triggering criteria category (block 530). For example,input component 310 may, as a result of detecting selection of atriggering criteria category, populate the user interface withinformation for the selected triggering criteria category. FIG. 6B is adiagram of an example user interface 600 that may be provided after amicrosite creator has selected a triggering criteria category. Assume,for explanatory purposes, that the microsite creator has already addedthe speed and motion categories and has now selected the locationcategory. In response, input component 310 may cause second area 620 tobecome populated with a criterion for the location category. Second area620 may allow the microsite creator to specify, for the locationcategory, a number of parameters 630 that, once provided, form thecriterion for the location category. In the example of FIG. 6B, thelocation category allows the microsite creator to specify, as parameters630, whether a user is or is not within some distance, in meters oranother unit of distance, of a particular location or object.

While the location category is shown as associated with one criterion,in some implementations, a triggering criteria category may include morethan one criterion. In such implementations, the microsite creator mayselect one or more of the available criteria for the triggering criteriacategory.

Process 500 may include receiving parameters for a criterion (block540). For example, input component 310 may receive parameters, frommicrosite creator device 220, relating to a triggering criterion. As anexample and with reference to FIG. 6B, the microsite creator may provideparameters 630 for the speed category, motion category, and locationcategory. As shown, the microsite creator has specified “running” and“4” for the motion category to form the criterion “motion pattern lookslike running for longer than 4 minutes.”

Returning to FIG. 5, process 500 may include determining whether anadditional triggering criteria category has been selected (block 550).For example, input component 310 may determine, for example, whether themicrosite creator has selected an additional triggering criteriacategory, from the list of triggering criteria categories. Additionally,or alternatively, input component 310 may determine whether themicrosite creator has selected a SUBMIT button or similar type ofbutton, which may indicate that the microsite creator has completedselecting triggering criteria categories.

In those situations where an additional triggering criteria category hasbeen selected (block 550—YES), process 500 may return to block 530 withinput component 310 populating the user interface with information forthe newly selected triggering criteria category. In those situationswhere an additional triggering criteria category has not been selected(block 550—NO), process 500 may include receiving parameters forcombining the selected triggering criteria (block 560). For example,input component 310 may provide a user interface to microsite creatordevice 220 that includes information identifying the selected triggeringcriteria. The microsite creator may, via the user interface, specify howthe selected triggering criteria are to be combined. In someimplementations, the user interface may provide the microsite creatorwith the ability to combine the selected triggering criteria using oneor more Boolean operators and/or parentheses. FIG. 6C is a diagram of anexample user interface 650 that may be provided to a microsite creatorto allow the microsite creator to combine selected triggering criteria.As shown, the microsite creator has combined, in area 660 of userinterface 650, the triggering criteria, selected in FIG. 6B, as follows:(SPEED OR MOTION) AND LOCATION. Thus, satisfying this triggeringcriteria requires the location criterion to be satisfied, as well aseither the speed criterion or the motion criterion. In someimplementations, area 660 may be pre-populated with the triggeringcriteria and possibly the Boolean operators selected in user interface600. The microsite creator may, however, modify the pre-populatedinformation in any desired manner.

While FIG. 5 shows process 500 as including a particular quantity andarrangement of blocks, in some implementations, process 500 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIG. 7 is a flowchart of an example process 700 for providing content ofa microsite. While FIG. 7 shows process 700 as including a particularsequence of interactions among user device 210, ranking system 230, anda server 240, in some implementations, some of these interactions mayoccur in another order or in parallel. Moreover, some of the blocks ofprocess 700 may be performed by a different device or group of devices,including or excluding user device 210, ranking system 230, and server240.

Process 700 may include obtaining sensor data (block 705). For example,user device 210 may obtain sensor data from sensors associated with userdevice 210. Examples of sensor data may include information regarding acurrent geographic location of user device 210; information regardingsounds occurring at or around user device 210; information regarding acurrent lighting condition at user device 210; information regarding acurrent date and/or time associated with user device 210; informationregarding a current speed of user device 210; information regarding acurrent direction in which user device 210 is moving; informationregarding a current orientation or change in orientation of user device210; information regarding a current weather condition in the locationin which user device 210 is located; information regarding a currenttemperature in the location in which user device 210 is located; and/orinformation regarding interaction of user device 210 with other deviceswith which user device 210 is in communication. While certain examplesof sensor data have been identified above, other types of sensor dataare possible.

Process 700 may include providing the sensor data (block 710). Forexample, user device 210 may provide the sensor data to ranking system230. In some implementations, user device 210 may also provide userprofile data to ranking system 230. Examples of user profile data mayinclude information regarding geographic addresses associated with theuser, such as the address of the user's home, the address of the user'splace of business, the address of a location frequented by the user,etc.; information inputted into a calendar associated with the user;information regarding the user's interaction with microsites that havebeen presented to the user, such as ratings given to the microsites,whether the user has dismissed—e.g., swiped away—from microsites thathave been presented to the user, or the like; information regarding theuser's communications, such as e-mails, text messages, instant messages,voicemail messages, or the like; information regarding the user'sactivity on the web, such as information regarding the user's searches,the user's browsing activity, the user's posts on social networks,blogs, and/or other public web sites; information regarding activitieson the web of the user's social contacts, such as the user's socialcontacts' posts on social networks, blogs, and/or other public websites; and/or information regarding the user's habits, such as placesthat the user has visited, things that the user has done, at what timethe user usually gets up in the morning, or the like. While certainexamples of user profile data have been identified above, other types ofuser profile data are possible.

User device 210 may automatically—e.g., without requiring an instructionfrom a user of user device 210—provide the sensor data and possibly theuser profile data to ranking system 230. The user, of user device 210,may stop, at any time, the sending of sensor data and/or user profiledata to ranking system 230. In addition, in some implementations, thesensor data and/or user profile data may be anonymized with regard tothe identity of the user.

Process 700 may further include receiving the sensor data (block 715).For example, ranking component 330, of ranking system 230, may receivethe sensor data from user device 210. In those situations where userdevice 210 also provides user profile data, ranking component 330 mayalso receive the user profile data.

Process 700 may include ranking microsites, identified using an index,based on the sensor data and the triggering criteria associated with themicrosites (block 720). For example, ranking component 330 may use thesensor data and, when provided, the user profile data, to identifyrelevant microsites. For example, ranking component 330 may compare thesensor data, and possibly the user profile data, to the triggeringcriteria for a microsite, identified by the index, and generate a scorefor the microsite based on a result of the comparison. As describedabove, in some implementations, ranking component 330 may modify thescore, for a microsite, based on one or more factors to generate a totalscore for the microsite. Ranking component 330 may use the score, ortotal score, to form a ranked list of microsites.

Process 700 may include providing information regarding the ranked listof microsites (block 725). For example, ranking component 330 mayprovide information regarding the ranked list of microsites to userdevice 210. As explained above, in some implementations, the informationmay include, for each microsite in the ranked list of microsites, anetwork address for the microsite and a list of sensors relevant to themicrosite.

Process 700 may include receiving the information regarding the rankedlist of microsites (block 730). For example, user device 210 may receivethe information regarding the ranked list of microsites from rankingcomponent 330.

Process 700 may include providing a request for a microsite in theranked list (block 735). For example, based on receiving the informationregarding the ranked list of microsites, user device 210 may obtainsensor data associated with the list of sensors that have beenidentified as relevant to the microsites in the ranked list. For eachrelevant microsite, user device 210 may generate a request that includesthe network address for the relevant microsite and the sensor datarelevant to the relevant microsite. User device 210 may provide therequest to one or more servers 240. Whether user device 210 provides therequests to more than one server 240 depends on which server(s) 240is/are hosting the relevant microsites. In other words, all of therelevant microsites may be hosted by a single server 240, all of therelevant microsites may be hosted by separate, different servers 240, orsomething in between these two extremes.

Process 700 may include receiving a request for a microsite (block 740).For example, server 240 may receive a request, for a microsite, fromuser device 210 and obtain content of the relevant microsite. In someimplementations, the content of a relevant microsite may be dynamic inthe sense that the content of the relevant microsite may be based on thesensor data received from user device 210.

Process 700 may include providing the microsite (block 745). Forexample, server 240 may provide the content of the relevant microsite touser device 210.

Process 700 may include receiving the content of the microsite (block750). For example, user device 210 may receive the content of themicrosite from server 240.

Process 700 may include rendering the content of the microsite (block755). For example, user device 210 may present the content of themicrosite on a display associated with user device 210. When content isreceived for multiple microsites, user device 210 may push the content,for the relevant microsites, as a sliding display of content. In someimplementations, content for one of the relevant microsites may bepresented on the display at a time. A user, of user device 210, mayinteract with the content, using a finger or the like, to express theuser's interest or disinterest in the content or to see the content foranother one of the relevant microsites.

A system and method, described herein, may allow a microsite creator tospecify triggering criteria that dictate when the creator's microsite isto be presented—e.g., pushed—to a user device. In some implementations,the microsite may be based on context data without the need for a user,of the user device, to request the microsite. The microsite may provideinformation that may be useful to the user.

Example 2

A system and/or method, as described herein, may provide a microsite toa user device based on context data and without the need for a user, ofthe user device, to request the microsite. The context data may includeuser profile data relating to the user or the user device and/or sensordata relating to one or more conditions associated with the user device.The microsite may provide information that may be useful to the user.

FIG. 8 is a diagram illustrating an overview of an exampleimplementation described herein. Assume that a user (“Mary”) is walkingin the city and has her mobile device with her. Mary has previouslyexpressed an interest in a movie called “The Action League Movie” byposting information about the movie on a social networking site; bycommunicating about the movie with her friend (e.g., via e-mail, textmessaging, instant messaging, etc.); by watching a trailer of the movieon the web; by searching for information regarding the movie on the web;or the like.

As shown in FIG. 8, a server may obtain context data relating to Maryand/or Mary's mobile device. The context data may include informationregarding Mary's interest in the movie, information regarding currentconditions (e.g., time, date, weather, etc.), information regarding thecurrent geographic location of Mary's mobile device, or the like. Theserver may use the context data to determine whether to trigger thepresentation of a microsite.

The server may store information regarding a group of microsites andcriteria for triggering the presentation of these microsites. The servermay compare the context data to the triggering criteria for themicrosites and use the comparison results to generate scores for themicrosites. The server may select a relevant microsite based on itsscore and provide information, regarding the relevant microsite, toMary's mobile device. In the example shown in FIG. 1, the relevantmicrosite may include details regarding an upcoming showing of TheAction League Movie. For example, Mary may be presented with informationthat a showing of the movie begins in eight minutes at the Regal Cinemaand information regarding how to get to the Regal Cinema (e.g., Mary maybe informed that the Regal Cinema is just two blocks away and an arrowmay identify the direction of the Regal Cinema relative to Mary'scurrent location). As a result, Mary may be presented with informationin which Mary is interested without the need for Mary to request theinformation.

FIG. 9 is a diagram of an example environment 900 in which systemsand/or methods described herein may be implemented. Environment 900 mayinclude multiple user devices 910 connected to ranking system 920, andmultiple servers 930-1, . . . , 930-N (N>1) (referred to collectively as“servers 930,” and individually as “server 930”) via a network 940.Three user devices 910, one ranking system 920, and N servers 930 havebeen illustrated as connected to network 940 for simplicity. Inpractice, there may be additional or fewer user devices, rankingsystems, servers, and/or networks. Also, in some instances, a userdevice 910 may perform a function described below as being performed byranking system 920, and/or ranking system 920 may perform a functiondescribed below as being performed by a user device 910.

User device 910 may include a client device, or a collection of clientdevices, that is capable of presenting a microsite on a display.Examples of user device 910 may include a smart phone, a personaldigital assistant, a laptop, a tablet computer, a personal computer, awatch, a gaming device, or a combination of these and/or other devices.User device 910 may include one or more browsers via which micrositesmay be presented on a display associated with user device 910.

Ranking system 920 may include a server device or a collection of serverdevices which may be co-located or remotely located. Ranking system 920may identify microsites and index information associated with themicrosites. Ranking system 920 may identify relevant microsites topresent to a user device 910, based on context data received from userdevice 910 and criteria for triggering the presentation of themicrosites, and provide information regarding the relevant microsites touser device 910.

Server 930 may include a server device or a collection of server devicesthat may be co-located or remotely located. Any two or more of servers930 may be implemented within a single, common server device or asingle, common collection of server devices. Servers 930 may hostmicrosites. In some implementations, one or more of servers 930 may beaffiliated with a same entity (e.g., party, organization, business,company, etc.) as ranking system 920. In some implementations, none ofservers 930 may be affiliated with the same entity as ranking system920.

While ranking system 920 is shown as separate from servers 930, it maybe possible for ranking system 920 to perform one or more of thefunctions described as being performed by a server 930 and/or a server930 to perform one or more of the functions described as being performedby ranking system 920. For example, ranking system 920 may host some ofthe microsites. Additionally, or alternatively, a user device 910 mayhost some of the microsites.

While ranking system 920 is shown as separate from user device 910, itmay be possible for user device 910 to perform one or more of thefunctions described as being performed by ranking system 920 and/orranking system 920 to perform one or more of the functions described asbeing performed by user device 910.

Network 940 may include any type of network, such as a local areanetwork (“LAN”), a wide area network (“WAN”), a telephone network, suchas the Public Switched Telephone Network (“PSTN”) or a cellular network,an intranet, the Internet, or a combination of networks. User devices910, ranking system 920, and servers 930 may connect to network 940 viawired and/or wireless connections. In other words, any one of userdevices 910, ranking system 920, and/or servers 930 may connect tonetwork 940 via a wired connection, a wireless connection, or acombination of a wired connection and a wireless connection.

FIG. 10 is a diagram of example functional components of user device910. In some implementations, the functional components, shown in FIG.10, may be implemented by user device 910. In some implementations, oneor more of the functional components, shown in FIG. 10, may beimplemented by a device separate from user device 910, such as anotheruser device 910 operating in combination with user device 910.

As shown in FIG. 10, user device 910 may include an application module1010, a user profile module 1020, a sensors module 1030, and a displaymodule 1040. In some implementations, user device 910 may includeadditional or fewer functional components than are illustrated in FIG.10.

Application module 1010 may control the operation of user device 910with regard to the presentation of microsites on user device 910. Insome implementations, application module 1010 may take the form of abrowser application. In some implementations, application module 1010may automatically run when user device 910 powers on or boots up, or mayrun when instructed by a user of user device 910. In someimplementations, application module 1010 may run in the background onuser device 1010. The user, of user device 910, may stop applicationmodule 1010 from running at any time.

Application module 1010 may obtain information from user profile module1020 and sensors module 1030 and provide the information to rankingsystem 920. Application module 1010 may also receive informationregarding one or more microsites from ranking system 920. In someimplementations, the information, regarding a microsite, may include anetwork address, such as a URL or URI, associated with the micrositefrom ranking system 920. Additionally, or alternatively, theinformation, regarding a microsite, may include a list of sensors thatis relevant to the content of the microsite. Application module 1010 mayprovide the information to display module 1040. In some implementations,application module 1010 may automatically obtain information from userprofile module 1020 and/or sensors module 1030, and/or automaticallyprovide the information to ranking system 920—e.g., without input from auser of user device 910. In some implementations, application module1010 may periodically provide the information to ranking system920—e.g., according to no predefined schedule. In some implementations,application module 1010 may regularly provide the information to rankingsystem 920—e.g., according to a predefined schedule. In someimplementations, application module 1010 may provide the information toranking system 920 based on a schedule identified by the user of userdevice 910—e.g., every 5 minutes between 10 AM and 11 PM when userdevice 910 has been idle for at least 5 minutes but not when user device910 is charging. In some implementations, application module 1010 mayprovide the information to ranking system 920 according to some othercriteria.

User profile module 1020 may obtain, store, and/or provide user profiledata. User profile data may include various information regarding userdevice 910, a user of user device 910, and/or one or more other userdevices 910 associated with the user of user device 910. The userprofile data may only be obtained, stored, and/or provided with theuser's express permission, and the user profile data may be anonymizedwith regard to the identity of the user. In some implementations, userprofile module 1020 may store some user profile data and an identifierassociated with additional user profile data, which may be storedexternally to user device 910, such as at ranking system 920 or at aserver accessible by ranking system 920. In some implementations, userprofile module 1020 may simply store an identifier associated with theuser profile data, which may be stored externally to user device 910,such as at ranking system 920 or at a server accessible by rankingsystem 920. Thus, references, herein, to user profile data may refer toan identifier associated with the user profile data.

Examples of user profile data may include information regardinggeographic addresses associated with the user, such as the address ofthe user's home, the address of the user's place of business, theaddress of a location frequented by the user, etc.; information inputtedinto a calendar associated with the user; information regarding theuser's interaction with microsites that have been presented to the user,such as ratings given to the microsites, whether the user hasdismissed—e.g., swiped away—from microsites that have been presented tothe user, or the like; information regarding the user's communications,such as e-mails, text messages, instant messages, voicemail messages, orthe like; information regarding the user's activity on the web, such asinformation regarding the user's searches, the user's browsing activity,the user's posts on social networks, blogs, and/or other public websites; information regarding the user's social contacts, such asidentifiers—e.g., identifiers that are anonymized with regard to theidentities of particular individuals—associated with people listed inthe user's address book, people friended by the user on social networksor other public web sites, people with whom the user has communicated,or other people having a social relationship with the user; and/orinformation regarding the user's habits, such as places that the userhas visited, things that the user has done, at what time the userusually gets up in the morning, or the like. While certain examples ofuser profile data have been identified above, other types of userprofile data are possible.

The user may review, add, remove, and/or revise the user profile data atany time. In some implementations, the user may specify what type ofinformation is to be used for the user profile data. For example, theuser may specify that the information regarding the user's activity onthe web is to be used for the user profile data, and the informationregarding the user's communications and the information regarding theuser's friends' activities on the web are not to be used for userprofile data.

Sensors module 1030 may obtain, store, and/or provide sensor data.Sensor data may include various information regarding user device 910and/or conditions associated with user device 910. The sensor data mayonly be obtained, stored, and/or provided with the user's expresspermission, and the sensor data may be anonymized with regard to theidentity of the user. Sensor module 1030 may interact with one or morecomponents of user device 910, such as an accelerometer, a globalpositioning system component, a communication component, or the like, toobtain the sensor data. Additionally, or alternatively, sensor module1030 may interact with one or more external devices, such as one or moreservers 930, to obtain the sensor data.

Examples of sensor data may include information regarding a currentgeographic location of user device 910; information regarding soundsoccurring at or around user device 910; information regarding currentlighting condition at user device 910; information regarding a currentdate and/or time associated with user device 910; information regardinga current speed of user device 910; information regarding a currentdirection in which user device 910 is moving; information regarding acurrent orientation or change in orientation of user device 910;information regarding a current weather condition in the location inwhich user device 910 is located; information regarding a currenttemperature in the location in which user device 910 is located; and/orinformation regarding interaction of user device 910 with other deviceswith which user device 910 is in communication. While certain examplesof sensor data have been identified above, other types of sensor dataare possible.

The user may specify what type of information is to be used for thesensor data. For example, the user may specify that the currentgeographic location, the current time, the current speed, the currentdirection, and the current orientation or change in orientation of userdevice 910 are to be used for the sensor data, and the interaction ofuser device 910 with other devices is not to be used for the sensordata.

Display module 1040 may receive information, such as a network addressassociated with a microsite and/or a list of sensors that are relevantto the microsite, from application module 1010. Display module 1040 mayuse the information to transmit a request to a server 930 to obtain thecontent of the microsite. The request may include the network address,associated with the microsite, and sensor data associated with thesensors in the list. The sensor data, included with the request, may bea subset of the sensor data obtained by sensors module 1030. In someparticular implementations, the request may include a GET request andthe content of the microsite may include hypertext mark-up language(HTML), cascading style sheets (CSS), or Javascript.

Display module 1040 may receive the content of the microsite and renderthe content of the microsite on a display associated with user device910. In some implementations, the content of the microsite may includecode to obtain real-time sensor data from user device 910 or a deviceseparate from user device 910. In some example implementations, thiscode may obtain the real-time sensor data once when the content of themicrosite is rendered on the display. In some example implementations,this code may obtain the real-time sensor data more than once while thecontent of the microsite is rendered on the display. The content of themicrosite may be updated based on the real-time sensor data.

In some implementations, display module 1040 may push the content to thedisplay so as to override any content already on the display. In someimplementations, display module 1040 may determine an appropriate timeto render the content of the microsite, such as when user device 910 isidle for a particular amount of time, when user device 910 is in a lockmode, when user device 910 is in a particular orientation, or the like.In some implementations, a user of user device 910 may specify how andwhen the user will be presented with the content of a microsite. Forexample, the user may specify that the content of a microsite can onlybe presented between 8 AM and 8 PM on weekdays and between 12 PM and 11PM on weekends; that the content of a microsite can only be presentedwhen the user is located in her home state of Virginia; that the contentof a microsite can only be presented when the user is moving at a speedof less than 20 KPH; or the like.

In some implementations, display module 1040 may present the content ofthe microsite on the display of user device 910 for a particular amountof time and, thereafter, remove the content of the microsite from thedisplay. In some example implementations, the particular amount of timemay be configurable by the user of user device 910. In some exampleimplementations, the particular amount of time may be preset byapplication module 1010, by an entity associated with ranking system920, or by an entity associated with server 930 hosting the content ofthe microsite.

In some implementations, display module 1040 may present the content ofthe microsite within a particular region of the display of user device910. The particular region may include the entire display area of thedisplay or a subset of the entire display area of the display. In someexample implementations, the size and/or location of the particularregion may be configurable by the user of user device 910. In someexample implementations, the size and/or location of the particularregion may be preset by application module 1010, by an entity associatedwith ranking system 920, or by an entity associated with server 930hosting the content of the microsite.

A user may interact with the content of the microsite to dismiss thecontent—e.g., by swiping the content—or to obtain additional informationregarding the content—e.g., by selecting the content. The user'sinteraction with the microsite content may be recorded as user profiledata by user profile module 1020.

FIG. 11 is a diagram of example functional components of ranking system920. In some implementations, the functional blocks, shown in FIG. 11,may be implemented by ranking system 920. In some implementations, oneor more of the functional components, shown in FIG. 11, may beimplementation by a device separate from or in combination with rankingsystem 920.

As shown in FIG. 11, ranking system 920 may include an input module1110, an indexing module 1120, and a ranking module 1130. In someimplementations, ranking system 920 may include additional or fewerfunctional components than are illustrated in FIG. 11.

Input module 1110 may identify microsites for use by ranking system 920.In some implementations, input module 1110 may identify micrositesthrough crawling. For example, input module 1110 may include or interactwith a crawler to locate microsites on a network, such as network 940.The crawler may follow links to locate documents on the network. Inputmodule 1110 may determine which documents are micro sites by locatingparticular information on documents that are microsites. This particularinformation may include a piece of code that identifies the document asa microsite. In some implementations, the particular information mayalso include triggering criteria that specifies criteria for when themicrocode is a candidate for presentation on a user device 910 and/or alist of sensors that are relevant to the microsite.

In some implementations, input module 1110 may identify microsites viamanual input. For example, input module 1110 may provide a userinterface via which users may provide information regarding micrositesthat the users have created. In some implementations, a user, via theuser interface, may identify a network address associated with amicrosite and/or may specify triggering criteria and a list of sensorsthat are relevant for the microsite. Additionally, or alternatively, theuser, via the user interface, may upload the content of the microsite.The content of the microsite may be hosted by ranking system 920 or adevice separate from ranking system 920, such as a server 930.

Indexing module 1120 may include one or more indexes that may be storedin one or more memory devices, which may be co-located or remotelylocated. In some implementations, indexing module 1120 may storeinformation regarding various microsites in an index. For a particularmicrosite, for example, the index may store a descriptive name of theparticular microsite, a network address for the particular microsite,triggering criteria for the particular microsite, and/or a list ofsensors that are relevant for the particular microsite. Ranking module1130 may use the information in the index to identify microsites thatare relevant for a particular user and/or in a particular situation.

Ranking module 1130 may receive user profile data and sensor data from auser device 910. Ranking module 1130 may use the user profile dataand/or the sensor data to identify relevant microsites. In someimplementations, ranking module 1130 may identify microsites that arerelevant based on the sensor data and the triggering criteria, comparethe sensor data to the triggering criteria for the microsites, andgenerate scores for the microsites based on result of the comparisons.For example, ranking module 1130 may perform a first analysis toidentify relevant microsites based on the sensor data and the triggeringcriteria; and perform a second analysis on the relevant microsites,based on a comparison of the sensor data and the triggering criteria, togenerate a score for each of the relevant microsites.

In some implementations, ranking module 1130 may identify micrositesthat are relevant to information in the user profile data, compare thesensor data to the triggering criteria for the microsites, and generatescores for the microsites based on result of the comparisons. Forexample, ranking module 1130 may perform a first analysis to identifymicrosites based on the user profile data; perform a second analysis toidentify relevant microsites based on the sensor data and the triggeringcriteria; and perform a third analysis on the relevant microsites, basedon a comparison of the sensor data and the triggering criteria, togenerate a score for each of the relevant microsites.

In some implementations, ranking module 1130 may modify the score, of amicrosite, based on one or more factors. For example, ranking module1130 may modify the score, of a microsite, based on a popularity scoreof the microsite. In some implementations, the popularity score of amicrosite may be generated based on user behavior data associated withthe microsite, such as how many users expressed disinterest in themicrosite by, for example, swiping away from the microsite or providinga negative rating when the microsite was presented to a user device 910,and/or how many users expressed interest in the microsite by, forexample, providing a positive rating when the microsite was presented toa user device 910, requesting additional information regarding themicrosite, or purchasing a service associated with the microsite. Insome implementations, the popularity score of a microsite may begenerated using one or more factors instead of, or in addition to, theuser behavior data, such as a quantity of times that the microsite hasbeen presented to user devices 910, an age of the microsite, a priorranking or score of the microsite, or the like.

Additionally, or alternatively, ranking module 1130 may modify thescore, of a microsite, based on a personalization score of themicrosite. In some implementations, the personalization score of amicrosite may be generated based on the user profile data, such as useractivity data, associated with a user of a particular user device 910,with regard to the microsite. The user activity data may include, forexample, whether the user has expressed disinterest in the microsite by,for example, swiping away from the microsite or providing a negativerating when the microsite was presented to the particular user device910, and/or whether the user expressed interest in the microsite by, forexample, providing a positive rating when the microsite was presented tothe particular user device 910, requesting additional informationregarding the microsite, purchasing a service or product associated withthe microsite, bookmarking the microsite, orienting the particular userdevice 910 to view the microsite without swiping away from themicrosite, and/or following a recommendation provided by themicrosite—e.g., a recommendation to visit a particular restaurant, see aparticular movie, ride a particular bus, or the like. In someimplementations, the personalization score of a microsite may begenerated using one or more factors instead of, or in addition to, theuser profile data, such as whether the user has recommended themicrosite to one of the user's friends.

Additionally, or alternatively, ranking module 1130 may modify thescore, of a microsite, based on a social score of the microsite. In someimplementations, the social score of a microsite may be generated basedon friend activity data, associated with social contacts—e.g.,friends—of the user of a particular user device 910, with regard to themicrosite. The user's friends may be identified based on the user'scommunications, the user's address book, and/or the user's account onone or more social networks. Examples of friend activity data,associated with a microsite, include whether the user's friends haveexpressed disinterest in the microsite by, for example, swiping awayfrom the microsite or providing a negative rating when the microsite waspresented to the friends' user devices 910, and/or whether the user'sfriends expressed interest in the microsite by, for example, providing apositive rating when the microsite was presented to the friends' userdevices 910, requesting additional information regarding the microsite,purchasing a service associated with the microsite, bookmarking themicrosite, and/or following a recommendation provided by themicrosite—e.g., a recommendation to visit a particular restaurant, see aparticular movie, ride a particular bus, or the like. In someimplementations, the social score of a microsite may be generated usingone or more factors instead of, or in addition to, the friend activitydata, such as whether the friends have recommended the microsite toothers.

In some implementations, ranking module 1130 may generate a total scorefor a microsite based on a combination of the score and the popularityscore, the personalization score, and/or the social score. In someimplementations, ranking module 1130 may generate a total score for amicrosite based on a combination of the score, the popularity score, thepersonalization score, and the social score. In some implementations,ranking module 1130 may generate a total score for a microsite based ona weighted combination of the score, the popularity score, thepersonalization score, and the social score. For example, ranking module1130 may assign a weight value to the score, the popularity score, thepersonalization score, and/or the social score. The weight values maydiffer—in other words, the amount that each of the score, the popularityscore, the personalization score, and the social score contributes tothe total score may vary. Rank module 1130 may combine the weightedscore, the weighted popularity score, the weighted personalizationscore, and/or the weighted social score to generate the total score.

Ranking module 1130 may select a set of microsites based on theirscores. For example, ranking module 1130 may select the top scoring Xmicrosites (X>1). In some implementations, ranking module 1130 mayselect only the top scoring microsite (X=1). In some implementations,ranking module 1130 may select the top scoring five (5) microsites(X=5).

Ranking module 1130 may provide information, regarding the set ofmicrosites, to user device 910. In some implementations, the informationmay include a network address and/or a list of sensors for eachmicrosite in the set of microsites. In some implementations, the networkaddresses of the microsites may be provided in a ranked list based onthe scores of the microsites. In some implementations, the networkaddresses of the microsites may be provided along with the scores of themicrosites.

FIG. 12 is a flowchart of an example process 1200 for presenting contentof a microsite. In some implementations, process 1200 may be performedby user device 910. In some implementations, one or more blocks ofprocess 1200 may be performed by one or more devices instead of, orpossibly in conjunction with, user device 910.

Process 1200 may include receiving user profile data (block 1210). Forexample, user profile module 1020, of user device 910, may receive andstore user profile data associated with user device 910 and/or a user ofuser device 910. User profile module 1020 may receive user profile datafrom the user and/or may receive user profile data from one or moreother components or programs of user device 910. Examples of userprofile data have been identified above. User profile module 1020 mayprovide the user profile data to application module 1010.

Process 1200 may include receiving sensor data (block 1220). Forexample, sensors module 1030, of user device 910, may receive and storesensor data associated with user device 910. Sensors module 1030 mayreceive sensor data from one or more components of user device 910and/or may receive sensor data from one or more devices external to userdevice 910, such as one or more servers 930 and/or one or more otheruser devices 910. Examples of sensor data have been identified above.Sensors module 1030 may provide the sensor data to application module1010.

Process 1200 may include providing the user profile data and the sensordata to ranking system 920 (block 1230). In some implementations,application module 1010, of user device 910, may periodically orregularly provide the user profile data and the sensor data to rankingsystem 920. Application module 1010 may provide the user profile dataand the sensor data to ranking system 920 automatically—e.g., withoutuser input.

As described above, ranking system 920 may receive the user profile dataand the sensor data from user device 910. Ranking system 920 may use theuser profile data and/or the sensor data to identify a set of relevantmicrosites. Ranking system 920 may compare the sensor data to thetriggering criteria for a microsite and generate a score for themicrosite based on a result of the comparison. As described above,ranking system 920 may modify the score based on one or more factors,such as a popularity score, a personalization score, and/or a socialscore. Ranking system 920 may select a set of microsites based on theirscores and provide information, regarding the set of microsites, to userdevice 910.

Process 1200 may include receiving information regarding a set ofmicrosites from ranking system 920 (block 1240). For example,application module 1010, of user device 910, may receive information,such as network addresses and lists of sensors, for the set ofmicrosites.

Process 1200 may include sending a request for a microsite with sensordata to a server 930 (block 1250). For example, display module 1040 may,for each microsite in the set of microsites, send a request to a server930 that hosts the microsite. Display module 1040 may use the networkaddress, associated with the microsite, to send the request and providesensor data associated with the list of sensors that are relevant to themicrosite. In some implementations, as described above, the request maytake the form of a GET request.

Process 1200 may include receiving microsite content from server 930(block 1260). In response to sending the request and the sensor data toserver 930, server 930 may identify the microsite content to send touser device 910. The microsite content may be dynamic in the sense thatthe content may change depending on the sensor data received from userdevice 910. For example, if the microsite relates to an exercisemicrosite, server 930 may receive information regarding the currentgeographic location, the current speed, and the current direction ofuser device 910, and may generate the microsite content based on thisinformation. Server 930 may send the microsite content to display module1040 of user device 910. Display module 1040 may receive the micrositecontent from server 930.

Process 1200 may display the microsite content (block 1270). Forexample, display module 1040 may cause the microsite content to appearon a display associated with user device 910. In some implementations,display module 1040 may determine whether it is an appropriate time todisplay the micro site content. For example, display module 1040 maydetermine whether user device 910 has been idle for a particular amountof time and cause the microsite content to be displayed only if userdevice 910 has been idle for at least the particular amount of time.Alternatively, or additionally, display module 1040 may determinewhether user device 910 is in a lock mode and cause the micrositecontent to be displayed only if user device 910 is in the lock mode.Alternatively, or additionally, display module 1040 may use anotherfactor to determine whether to cause the microsite content to bedisplayed.

While FIG. 12 shows process 1200 as including a particular quantity andarrangement of blocks, in some implementations, process 1200 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIG. 13 is a flowchart of example process 1300 for providing informationregarding a set of microsites. In some implementations, process 1300 maybe performed by ranking system 920. In some implementations, one or moreblocks of process 1300 may be performed by one or more devices insteadof, or possibly in conjunction with, ranking system 920.

Process 1300 may include receiving microsite information (block 1310).For example, input module 1110, of ranking system 920, may include orinteract with a crawler that locates microsites via a crawlingoperation. As described above, the microsites may be located based on apiece of code, located on the microsites, which identifies themicrosites as microsites. The microsites may be analyzed to identifyinformation regarding the microsites. Additionally, or alternatively,input module 1110 may receive information regarding microsites viamanual input via a user interface provided by input module 1110. In someimplementations, input module 1110 may receive or determine micrositeinformation, such as descriptive names of the microsites, networkaddresses associated with the microsites, triggering criteria thatspecify when the microsites may be identified for presentation, and/orlists of sensors that are relevant to the content of the microsites.

Process 1300 may include creating an index with the micrositeinformation (block 1320). For example, indexing module 1120, of rankingsystem 920, may store the microsite information in an index. For aparticular microsite, indexing module 1120 may store a descriptive namefor the particular microsite, a network address for the particularmicrosite, triggering criteria for the particular microsite, and/or alist of sensors for the particular microsite.

Process 1300 may include receiving user profile data and sensor datafrom user device 910 (block 1330). For example, as described above, userdevice 910 may automatically and periodically/regularly send userprofile data and sensor data to ranking system 920. Ranking module 1130,of ranking system 920, may receive the user profile data and the sensordata from user device 910.

Process 1300 may include searching the index, based on the user profiledata, the sensor data, and the triggering criteria, to identify relevantmicrosites (block 1340), and generating scores for the relevantmicrosites (block 1350). For example, ranking module 1130 may identifyrelevant microsites, in the index of indexing module 1120, based on theuser profile data and/or the sensor data, as described above. Rankingmodule 1130 may generate a score for a relevant microsite based on howwell the sensor data matches the triggering criteria for the relevantmicrosite. In some implementations, as described above, ranking module1130 may modify the score, for the microsite, based on one or morefactors, such as a popularity score, a personalization score, and/or asocial score for the microsite, to generate a total score for themicrosite.

Process 1300 may include providing information regarding top-scoringmicrosites (block 1360). For example, ranking module 1130 may select aset of the relevant microsites based on their scores, such as the topscoring X microsites. Ranking module 1130 may provide information,regarding the set of relevant microsites, to user device 910. In someimplementations, as described above, the information may include anetwork address and a list of sensors for each microsite in the set ofrelevant microsites. User device 910 may use the network address, of amicrosite, to retrieve the content of the microsite from a server 930.

While FIG. 13 shows process 1300 as including a particular quantity andarrangement of blocks, in some implementations, process 1300 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIG. 14 is a flowchart of example process 1400 for providing content ofa microsite. In some implementations, process 1400 may be performed byserver 930. In some implementations, one or more blocks of process 1400may be performed by one or more devices instead of, or possibly inconjunction with, server 930.

Process 1400 may include publishing a microsite (block 1410). Forexample, a user may create a microsite and store the content for themicrosite on server 930. Server 930 may host the microsite and connectto network 960 to make the microsite available to user devices 910 andranking system 920. In some implementations, ranking system 920 maycrawl the content of the microsite. In some implementations, the usermay upload information, regarding the microsite, to ranking system 920.

Process 1400 may include receiving a request with a network address andsensor data from a user device 910 (block 1420). For example, server 930may receive a request from a user device 910. As described above, userdevice 910 may use the network address of a microsite to access themicrosite. The content of the microsite may be dynamic in the sense thatthe content may be generated based on the sensor data. In other words,server 930 may generate the microsite content based on the sensor datareceived from user device 910. In some implementations, server 930 maysimply provide the content of the microsite without knowing the identityof user device 910 or identity of the user of user device 910.

Process 1400 may include providing microsite content to user device 910(block 1430). For example, server 930 may provide the microsite contentto user device 910. In some implementations, the microsite content maybe provided as HTML content, CSS content, or Javascript content.

While FIG. 14 shows process 1400 as including a particular quantity andarrangement of blocks, in some implementations, process 1400 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIG. 15 is a diagram of illustrating an example process flow 1500 thatinvolves user device 910, ranking system 920, and servers 930. WhileFIG. 15 shows process flow 1500 as including a particular sequence ofinteractions among user device 910, ranking system 920, and servers 930,in some implementation, some of these interactions may occur in anotherorder or in parallel.

As shown at (A) in FIG. 15, input module 1110, of ranking system 920,may identify microsites for use by ranking system 920. In someimplementations, as described above, input module 1110 may identifymicrosites through crawling and/or via manual input. In eithersituation, input module 1110 may obtain information regarding aparticular microsite, such as a descriptive name of the particularmicrosite, a network address for the particular microsite, triggeringcriteria for the particular microsite, and/or a list of sensors that arerelevant for the particular microsite.

As shown at (B) in FIG. 15, input module 1110, of ranking system 920,may provide information regarding various microsites to indexing module1120. Indexing module 1120 may store information regarding themicrosites in one or more indexes. In some implementations, as describedabove, indexing module 1120 may store, for a particular microsite in anindex, a descriptive name of the particular microsite, a network addressfor the particular microsite, triggering criteria for the particularmicrosite, and/or a list of sensors that are relevant for the particularmicrosite.

As shown at (C) in FIG. 15, application module 1010, of user device 910,may obtain user profile data from user profile module 1020 and/or mayobtain sensor data from sensors module 1030. The user profile data mayinclude various information regarding user device 910 and/or a user ofuser device 910. Examples of user profile data have been given above.The sensor data may include various information regarding user device910 and/or conditions associated with user device 910. Examples ofsensor data have been given above.

As shown at (D) in FIG. 15, application module 1010 may provide the userprofile data and/or the sensor data to ranking system 920. As describedabove, application module 1010 may automatically—e.g., without requiringan instruction from a user of user device 910—provide the user profiledata and/or the sensor data to ranking system 920. Ranking module 1130,of ranking system 920, may receive the user profile data and/or thesensor data.

As shown at (E) in FIG. 15, ranking module 1130 may use the user profiledata and/or the sensor data to identify relevant microsites. Asdescribed above, in some implementations, ranking module 1130 mayidentify relevant micro sites, in the index, based on the sensor dataand the triggering criteria, and generate a score for the relevantmicrosites based on a result of a comparison of the sensor data and thetriggering criteria. As also described above, in some implementations,ranking module 1130 may identify microsites, in the index, based on theuser profile data, determine which of these microsites is relevant basedon the sensor data and the triggering criteria, and generate a score forthe relevant microsites based on a result of a comparison of the sensordata and the triggering criteria. As described above, in someimplementations, ranking module 1130 may modify the score, for amicrosite, based on one or more factors to generate a total score forthe microsite. Ranking module 1130 may use the score, or total score, toidentify a set of relevant microsites.

As shown at (F) in FIG. 15, ranking module 1130 may provide information,regarding the set of relevant microsites, to user device 910. Asexplained above, in some implementations, the information may include,for each microsite in the set of relevant microsites, a network addressfor the microsite and a list of sensors relevant to the microsite.Application module 1010, of user device 910, may receive the informationregarding the set of relevant microsites.

As shown at (G) in FIG. 15, application module 1010 may provide theinformation, regarding the set of relevant microsites, to display module1040 of user device 910. Display module 1040 may receive the informationregarding the set of relevant microsites. Display module 1040 may obtainsensor data associated with the list of sensors that have beenidentified as relevant to the relevant microsites. For each relevantmicrosite, display module 1040 may generate a request that includes thenetwork address for the relevant microsite and the sensor data relevantto the relevant microsite.

As shown at (H) in FIG. 15, display module 1040 may transmit therequests to one or more servers 930. Whether display module 1040transmits the requests to more than one server 930 depends on whichserver(s) 930 is/are hosting the relevant microsites. In other words,all of the relevant microsites may be hosted by a single server 930, allof the relevant microsites may be hosted by separate, different servers930, or something in between these two extremes.

Server(s) 930 may receive the requests from user device 910 may obtaincontent of the relevant microsites. In some implementations, asdescribed above, the content of a relevant microsite may be dynamic inthe sense that the content of the relevant microsite is based on thesensor data received from user device 910.

As shown at (I) in FIG. 15, server(s) 930 may provide the content of therelevant microsites to user device 910. Display module 1040, of userdevice 910, may receive the content and present the content on a displayassociated with user device 910. For example, display module 1040 maypush the content, for the relevant microsites, as a sliding display ofcontent. In some implementations, content for one of the relevantmicrosites may be presented on the display at a time. A user, of userdevice 910, may interact with the content, using a finger or the like,to express the user's interest or disinterest in the content or to seethe content for another one of the relevant microsites.

FIG. 16 illustrates an example of microsite content that may bepresented in a certain context. As shown in FIG. 16, assume that a user(“Emma”) goes out for a run and takes, with her, a user device in theform of a watch. The watch sends user profile data and sensor data tothe ranking system. As shown in FIG. 16, assume that the user profiledata includes information identifying Emma's user profile—i.e.,ABC123—which may include any kind of identifier that the ranking systemmay use to locate Emma's user profile. The ranking system may obtainEmma's preferences from her user profile. As further shown in FIG. 16,assume that the sensor data includes information identifying the currentdate—i.e., Mar. 1, 2012; the current time i.e., 8:10 AM; the currentweather condition—i.e., sunny; Emma's current speed—i.e., 10 kilometersper hour (KPH); and Emma's current geographic location—i.e., latitude(LAT) 40.52202 and longitude (LONG) −79.84180.

Assume that the ranking system identifies, based on the user profiledata and the sensor data, that a Run Tracker microsite is relevant. Forexample, the Run Tracker microsite might have triggering criteria thatspecifies a condition that the user be moving at a speed between 3 KPHand 20 KPH during the hours between 6 AM and 8 PM. In this case, Emma'ssensor data indicates that she is moving at a speed of 10 KPH, which isbetween 3 KPH and 20 KPH, at 8:10 AM, which is between 6 AM and 8 PM.Thus, the ranking system identifies the Run Tracker microsite as arelevant microsite.

The ranking system may provide, to the watch, information associatedwith the Run Tracker microsite, such as a network address for themicrosite—i.e., run_tracker.com/123—and a list of sensors relevant tothe microsite—i.e., speed and location. The watch may receive theinformation associated with the Run Tracker microsite and generate arequest based on the information.

The watch may transmit the request, including the network address ofrun_tracker.com/123 and the sensor data that includes the speed of 10KPH and the location of LAT 40.52202 and LONG −79.84180, to a serverassociated with the Run Tracker microsite—hereinafter called the runtracker server. The run tracker server may process the sensor data togenerate and/or modify the content of the Run Tracker microsite. The runtracker server may provide the content of the Run Tracker microsite tothe watch. The watch may then display the content of the Run Trackermicrosite on its display. As shown in FIG. 16, the Run Tracker micrositemay display the distance that Emma has run and her current pace.

FIGS. 17A-17D illustrate examples of microsite content that may bepresented in a certain context. As shown in FIG. 17A, assume that a user(“Emma”) is walking to work and takes, with her, a user device in theform of a watch. The watch sends user profile data and sensor data tothe ranking system. As shown in FIG. 17A, assume that the user profiledata includes information identifying Emma's user profile—i.e.,ABC123—which may include any kind of identifier that the ranking systemmay use to locate Emma's user profile. The ranking system may obtainEmma's preferences from her user profile. As further shown in FIG. 17A,assume that the sensor data includes information identifying the currentdate—i.e., Mar. 2, 2012; the current time—i.e., 9:32 AM; the currentweather condition—i.e., sunny; Emma's current speed—i.e., 0.8 kilometersper hour (KPH); and Emma's current geographic location—i.e., latitude(LAT) 40.52202 and longitude (LONG) −79.84180.

Assume that the ranking system identifies, based on the user profiledata and the sensor data, that a Bus Notifier microsite is relevant. Forexample, the Bus Notifier microsite might have triggering criteria thatspecifies that the user be moving at a speed below 3 KPH and that theuser be located within 50 meters of a bus stop within 5 minutes of thescheduled time that a bus is going to arrive at the bus stop. In thiscase, Emma's sensor data indicates that she is moving at a speed of 0.8KPH, which is below 3 KPH, that she is located within 5 meters of a busstop, and that, based on the current time of 9:32 AM, a bus is scheduledto arrive in 2 minutes. Thus, the ranking system identifies the BusNotifier microsite as a relevant microsite.

The ranking system may provide, to the watch, information associatedwith the Bus Notifier microsite, such as a network address for themicrosite—i.e., busnotifier.com/123—and a list of sensors relevant tothe microsite—i.e., time and location. The watch may receive theinformation associated with the Bus Notifier microsite and generate arequest based on the information.

The watch may transmit the request, including the network address ofbusnotifier.com/123 and the sensor data that includes the current timeof 9:32 AM and the location of LAT 40.52202 and LONG −79.84180, to aserver associated with the Bus Notifier microsite—hereinafter called themetrobus notifier server. The metrobus notifier server may process thesensor data to generate and/or modify the content of the Bus Notifiermicrosite. The metrobus notifier server may provide the content of theBus Notifier microsite to the watch. The watch may then display thecontent of the Bus Notifier microsite on its display.

Assume, for the purposes of FIGS. 17B-17D, that, in the above example,the ranking system not only provided information regarding the BusNotifier microsite, but also provided information regarding a historymicrosite. Assume that the history microsite provides historical factsrelating to a user's location and the current day.

As shown in FIG. 17B, the watch may display the content of the BusNotifier microsite. Emma may interact with the content using, forexample, her finger. Assume that Emma is disinterested in the content ofthe Bus Notifier microsite and uses her finger to swipe away from theBus Notifier microsite. Information regarding Emma's disinterest in theBus Notifier microsite, as evidenced by her swiping away from the BusNotifier microsite, may be recorded as additional user profile data.

As shown in FIG. 17C, Emma swipes the screen of the watch with herfinger. As a result of the swiping action, the watch displays thecontent of the next microsite—i.e., the content of the historymicrosite, as shown in FIG. 17D. The history microsite indicates ahistorical fact relating to Emma's current location on this day—i.e.,Paul Revere's famous ride occurred on the street on which Emma iswalking on this day in 1775.

A system and method, described herein, may push a microsite to a userdevice based on context data without the need for a user, of the userdevice, to request the microsite. The microsite may provide informationthat may be useful to the user.

Example 3

A system and/or method, as described herein, may provide informationregarding a relevant microsite to a user device based on context data.The context data may include user profile data relating to the user orthe user device and/or sensor data relating to one or more conditionsassociated with the user device. The relevant microsite may bedetermined based on popularity data associated with the microsite,personalization data associated with the user, and/or social dataassociated with a social contact of the user. The microsite may provideinformation that may be useful to the user.

FIG. 18 is a diagram illustrating an overview of an exampleimplementation described herein. Assume that a user (“Mary”) is walkingin the city and has her mobile device with her. Mary's mobile device maysend sensor data, such as information regarding the current date andtime, Mary's current geographic location, Mary's current speed anddirection, or the like, to a ranking system.

The ranking system may maintain a microsite index. The microsite indexmay store information regarding microsites. For a particular microsite,the microsite index may store triggering criteria that indicates whenthe particular microsite is relevant. The ranking system may compare thesensor data, from Mary's mobile device, to the triggering criteria inthe microsite index to identify a set of relevant microsites.

The ranking system may generate scores for the relevant microsites basedon popularity data, personalization data, and/or social data. Thepopularity data, for a particular microsite, may reflect a measure ofpopularity of the particular microsite. Assume, for the example of FIG.18, that a microsite for the Rio Grand restaurant has been identified asa popular microsite. The personalization data may reflect a measure ofinterest, by a user, in the particular microsite. Assume, for theexample of FIG. 18, that Mary has expressed an interest in the Rio Grandrestaurant by, for example, accessing a web site associated with the RioGrand restaurant, entering information in her calendar regarding a lunchdate at the Rio Grand restaurant on more than one occasion, andcommunicating with a friend about meeting at the Rio Grand restaurant.The social data may reflect a measure of interest, by a social contactof the user, in the particular microsite. Assume, for the example ofFIG. 18, that Mary's friends Bob, Alice, and Diane have expressed aninterest in the Rio Grand restaurant by, for example, postinginformation regarding a recent dinner at the Rio Grand restaurant on asocial network, visiting the Rio Grand restaurant, and/or giving afavorable rating to the Rio Grand microsite.

The ranking system may select one or more of the relevant micrositesbased on the scores of the relevant microsites. Assume that the RioGrand microsite is the highest scoring microsite in the set of relevantmicrosites. As shown in FIG. 18, the ranking system may provideinformation regarding the Rio Grand microsite to Mary's mobile device.Mary's mobile device may, thereafter, display the content of the RioGrand microsite. As shown in FIG. 18, the content of the Rio Grandmicrosite may include information regarding the distance to therestaurant relative to Mary's current location and information regardingMary's friends' average rating. As a result, Mary may be presented withinformation in which Mary is interested without the need for Mary torequest the information.

FIG. 19 is a diagram of an example environment 1900 in which systemsand/or methods described herein may be implemented. Environment 1900 mayinclude multiple user devices 1910 connected to ranking system 1920, andmultiple servers 1930-1, . . . , 1930-N (N≥1) (referred to collectivelyas “servers 1930,” and individually as “server 1930”) via a network1940.

User device 1910 may include a client device, or a collection of clientdevices, that is capable of presenting a microsite on a display.Examples of user device 1910 may include a smart phone, a personaldigital assistant, a laptop, a tablet computer, a personal computer, awatch, a gaming device, or a combination of these and/or other devices.User device 1910 may include one or more browsers via which micrositesmay be presented on a display associated with user device 1910.

Ranking system 1920 may include a server device or a collection ofserver devices which may be co-located or remotely located. Rankingsystem 1920 may identify microsites and index information associatedwith the microsites. Ranking system 1920 may identify relevantmicrosites to present to a user device 1910, based on context datareceived from user device 1910 and criteria for triggering thepresentation of the microsites, generate scores for the relevantmicrosites based on popularity data, personalization data, and/or socialdata, and provide information regarding the relevant microsites, basedon the scores, to user device 1910.

Server 1930 may include a server device or a collection of serverdevices that may be co-located or remotely located. Any two or more ofservers 1930 may be implemented within a single, common server device ora single, common collection of server devices. Servers 1930 may hostmicrosites. In some implementations, one or more of servers 1930 may beaffiliated with a same entity (e.g., party, organization, business,company, etc.) as ranking system 1920. In some implementations, none ofservers 1930 may be affiliated with the same entity as ranking system1920.

While ranking system 1920 is shown as separate from servers 1930, it maybe possible for ranking system 1920 to perform one or more of thefunctions described as being performed by a server 1930 and/or a server1930 to perform one or more of the functions described as beingperformed by ranking system 1920. For example, ranking system 1920 mayhost some of the microsites. Additionally, or alternatively, a userdevice 1910 may host some of the microsites.

While ranking system 1920 is shown as separate from user device 1910, itmay be possible for user device 1910 to perform one or more of thefunctions described as being performed by ranking system 1920 and/orranking system 1920 to perform one or more of the functions described asbeing performed by user device 210.

Network 1940 may include any type of network, such as a local areanetwork (“LAN”), a wide area network (“WAN”), a telephone network, suchas the Public Switched Telephone Network (“PSTN”) or a cellular network,an intranet, the Internet, or a combination of networks. User devices1910, ranking system 1920, and servers 1930 may connect to network 1940via wired and/or wireless connections. In other words, any one of userdevices 1910, ranking system 1920, and/or servers 1930 may connect tonetwork 1940 via a wired connection, a wireless connection, or acombination of a wired connection and a wireless connection.

While FIG. 19 shows environment 1900 as having a particular quantity andarrangement of user devices 1910, ranking system 1920, servers 1930, andnetwork 1940, in some implementations, environment 1900 may includefewer, additional, or different user devices 1910, ranking system 1920,servers 1930, and network 1940 than are shown in FIG. 19.

FIG. 20 is a diagram of example functional components of user device1910. As shown in FIG. 20, user device 1910 may include an applicationmodule 2010, a user profile module 2020, a sensors module 2030, and adisplay module 2040. In some implementations, the functional components,shown in FIG. 20, may be implemented by user device 1910. In someimplementations, one or more of the functional components, shown in FIG.20, may be implemented by a device separate from user device 1910, suchas another user device 1910 operating in combination with user device1910.

Application module 2010 may control the operation of user device 1910with regard to the presentation of microsites on user device 1910. Insome implementations, application module 2010 may take the form of abrowser application. In some implementations, application module 2010may automatically run when user device 1910 powers on or boots up, ormay run when instructed by a user of user device 1910. In someimplementations, application module 2010 may run in the background onuser device 2010. The user, of user device 1910, may stop applicationmodule 2010 from running at any time.

Application module 2010 may obtain information from user profile module2020 and sensors module 2030 and provide the information to rankingsystem 1920. Application module 2010 may also receive informationregarding one or more microsites from ranking system 1920. In someimplementations, the information, regarding a microsite, may include anetwork address, such as a Uniform Resource Locator (URL) or UniformResource Identifier (URI), associated with the microsite from rankingsystem 1920. Additionally, or alternatively, the information, regardinga microsite, may include a list of sensors that is relevant to thecontent of the microsite. Application module 2010 may provide theinformation to display module 2040. In some implementations, applicationmodule 2010 may automatically obtain information from user profilemodule 2020 and/or sensors module 2030, and/or automatically provide theinformation to ranking system 1920—e.g., without input from a user ofuser device 1910. In some implementations, application module 2010 mayperiodically provide the information to ranking system 1920—e.g.,according to no predefined schedule. In some implementations,application module 2010 may regularly provide the information to rankingsystem 1920—e.g., according to a predefined schedule. In someimplementations, application module 2010 may provide the information toranking system 1920 based on a schedule identified by the user of userdevice 1910—e.g., every 5 minutes between 10 AM and 11 PM when userdevice 1910 has been idle for at least 5 minutes but not when userdevice 1910 is charging. In some implementations, application module2010 may provide the information to ranking system 1920 according tosome other criteria.

User profile module 2020 may obtain, store, and/or provide user profiledata. User profile data may include various information regarding userdevice 1910, a user of user device 1910, and/or one or more other userdevices 1910 associated with the user of user device 1910. The userprofile data may only be obtained, stored, and/or provided with theuser's express permission, and the user profile data may be anonymizedwith regard to the identity of the user. In some implementations, userprofile module 2020 may store some user profile data and an identifierassociated with additional user profile data, which may be storedexternally to user device 1910, such as at ranking system 1920 or at aserver or another device accessible by ranking system 1920. In someimplementations, user profile module 2020 may simply store an identifierassociated with the user profile data, which may be stored externally touser device 1910, such as at ranking system 1920 or at a server oranother device accessible by ranking system 1920. Thus, references,herein, to user profile data may refer to an identifier associated withthe user profile data.

Examples of user profile data may include information regardinggeographic addresses associated with the user, such as the address ofthe user's home, the address of the user's place of business, theaddress of a location frequented by the user, etc.; information inputtedinto a calendar associated with the user; information regarding theuser's interaction with microsites that have been presented to the user,such as ratings given to the microsites, whether the user hasdismissed—e.g., swiped away—from microsites that have been presented tothe user, or the like; information regarding the user's communications,such as e-mails, text messages, instant messages, voicemail messages, orthe like; information regarding the user's activity on the web, such asinformation regarding the user's searches, the user's browsing activity,the user's posts on social networks, blogs, and/or other public websites; information regarding the user's social contacts, such asidentifiers—e.g., identifiers that are anonymized with regard to theidentities of particular individuals—associated with people listed inthe user's address book, people friended by the user on social networksor other public web sites, people with whom the user has communicated,or other people having a social relationship with the user; and/orinformation regarding the user's habits, such as places that the userhas visited, things that the user has done, at what time the userusually gets up in the morning, or the like. While certain examples ofuser profile data have been identified above, other types of userprofile data are possible.

The user may review, add, remove, and/or revise the user profile data atany time. In some implementations, the user may specify what type ofinformation is to be used for the user profile data and for whatpurpose. For example, the user may specify that the informationregarding the user's activity on the web is to be used for the userprofile data, and the information regarding the user's communications isnot to be used for user profile data. Additionally, or alternatively,the user may specify that all or some of the user profile data may beused for generating a personalization score—described below—that can beused when determining what microsite content to present to the user.Additionally, or alternatively, the user may specify that all or some ofthe user profile data may be used for generating a socialscore—described below—that can be used when determining what micrositecontent to present to another user, for whom the user is a socialcontact.

Sensors module 2030 may obtain, store, and/or provide sensor data.Sensor data may include various information regarding user device 1910and/or conditions associated with user device 1910. The sensor data mayonly be obtained, stored, and/or provided with the user's expresspermission, and the sensor data may be anonymized with regard to theidentity of the user. Sensor module 2030 may interact with one or morecomponents of user device 1910, such as an accelerometer, a globalpositioning system component, a communication component, or the like, toobtain the sensor data. Additionally, or alternatively, sensor module2030 may interact with one or more external devices, such as one or moreservers 1930 or other user devices, to obtain the sensor data.

Examples of sensor data may include information regarding a currentgeographic location of user device 1910; information regarding soundsoccurring at or around user device 1910; information regarding currentlighting condition at user device 1910; information regarding a currentdate and/or time associated with user device 1910; information regardinga current speed of user device 1910; information regarding a currentdirection in which user device 1910 is moving; information regarding acurrent orientation or change in orientation of user device 1910;information regarding a current weather condition in the location inwhich user device 1910 is located; information regarding a currenttemperature in the location in which user device 1910 is located; and/orinformation regarding interaction of user device 1910 with other deviceswith which user device 1910 is in communication. While certain examplesof sensor data have been identified above, other types of sensor dataare possible.

The user may specify what type of information is to be used for thesensor data. For example, the user may specify that the currentgeographic location, the current time, the current speed, the currentdirection, and the current orientation or change in orientation of userdevice 1910 are to be used for the sensor data, and the interaction ofuser device 1910 with other devices is not to be used for the sensordata.

Display module 2040 may receive information, such as a network addressassociated with a microsite and/or a list of sensors that are relevantto the microsite, from application module 2010. Display module 2040 mayuse the information to transmit a request to a server 1930 to obtain thecontent of the microsite. The request may include the network address,associated with the microsite, and sensor data associated with thesensors in the list. The sensor data, included with the request, may bea subset of the sensor data obtained by sensors module 2030. In someparticular implementations, the request may include a GET request andthe content of the microsite may include hypertext mark-up language(HTML), cascading style sheets (CSS), or Javascript.

Display module 2040 may receive the content of the microsite and renderthe content of the microsite on a display associated with user device1910. In some implementations, the content of the microsite may includecode to obtain real-time sensor data from user device 1910 or a deviceseparate from user device 1910. In some example implementations, thiscode may obtain the real-time sensor data once when the content of themicrosite is rendered on the display. In some example implementations,this code may obtain the real-time sensor data more than once while thecontent of the microsite is rendered on the display. The content of themicrosite may be updated based on the real-time sensor data.

In some implementations, display module 2040 may push the content to thedisplay so as to override any content already on the display. In someimplementations, display module 2040 may determine an appropriate timeto render the content of the microsite, such as when user device 1910 isidle for a particular amount of time, when user device 1910 is in a lockmode, when user device 1910 is in a particular orientation, or the like.In some implementations, a user of user device 1910 may specify how andwhen the user will be presented with the content of a microsite. Forexample, the user may specify that the content of a microsite can onlybe presented between 8 AM and 8 PM on weekdays and between 12 PM and 11PM on weekends; that the content of a microsite can only be presentedwhen the user is located in her home state of Virginia; that the contentof a microsite can only be presented when the user is moving at a speedof less than 20 KPH; or the like.

In some implementations, display module 2040 may present the content ofthe microsite on the display of user device 1910 for a particular amountof time and, thereafter, remove the content of the microsite from thedisplay. In some example implementations, the particular amount of timemay be configurable by the user of user device 1910. In some exampleimplementations, the particular amount of time may be preset byapplication module 2010, by an entity associated with ranking system1920, or by an entity associated with server 1930 hosting the content ofthe microsite.

In some implementations, display module 2040 may present the content ofthe microsite within a particular region of the display of user device1910. The particular region may include the entire display area of thedisplay or a subset of the entire display area of the display. In someexample implementations, the size and/or location of the particularregion may be configurable by the user of user device 1910. In someexample implementations, the size and/or location of the particularregion may be preset by application module 2010, by an entity associatedwith ranking system 1920, or by an entity associated with server 1930hosting the content of the microsite.

A user may interact with the content of the microsite to dismiss thecontent—e.g., by swiping the content—or to obtain additional informationregarding the content—e.g., by selecting the content. The user'sinteraction with the microsite content may be recorded as user profiledata by user profile module 2020.

While FIG. 20 shows user device 1910 as having a particular quantity andarrangement of functional components, in some implementations, userdevice 1910 may include fewer functional components, additionalfunctional components, or different functional components than are shownin FIG. 20.

FIG. 21 is a diagram of example functional components of ranking system1920. In some implementations, the functional blocks, shown in FIG. 21,may be implemented by ranking system 1920. In some implementations, oneor more of the functional components, shown in FIG. 21, may beimplemented by a device separate from or in combination with rankingsystem 1920.

As shown in FIG. 21, ranking system 1920 may include an input module2110, an indexing module 2120, and a ranking module 2130. In someimplementations, ranking system 1920 may include additional or fewerfunctional components than are illustrated in FIG. 21.

Input module 2110 may identify microsites for use by ranking system1920. In some implementations, input module 2110 may identify micrositesthrough crawling. For example, input module 2110 may include or interactwith a crawler to locate microsites on a network, such as network 1940.The crawler may follow links to locate documents on the network. Inputmodule 2110 may determine which documents are micro sites by locatingparticular information on documents that are microsites. This particularinformation may include a piece of code that identifies the document asa microsite. In some implementations, the particular information mayalso include triggering criteria that specifies criteria for when themicrocode is a candidate for presentation on a user device 1910 and/or alist of sensors that are relevant to the microsite.

In some implementations, input module 2110 may identify microsites viamanual input. For example, input module 2110 may provide a userinterface via which users may provide information regarding micrositesthat the users have created. In some implementations, a user, via theuser interface, may identify a network address associated with amicrosite and/or may specify triggering criteria and a list of sensorsthat are relevant for the microsite. Additionally, or alternatively, theuser, via the user interface, may upload the content of the microsite.The content of the microsite may be hosted by ranking system 1920 or adevice separate from ranking system 1920, such as a server 1930.

Indexing module 2120 may include one or more indexes that may be storedin one or more memory devices, which may be co-located or remotelylocated. In some implementations, indexing module 2120 may storeinformation regarding various microsites in an index. For a particularmicrosite, for example, the index may store a descriptive name of theparticular microsite, a network address for the particular microsite,triggering criteria for the particular microsite, and/or a list ofsensors that are relevant for the particular microsite. Ranking module2130 may use the information in the index to identify microsites thatare relevant for a particular user and/or in a particular situation.

FIG. 22 is a diagram of an example entry 2200 that may be stored in anindex maintained by indexing module 2120. Each entry in the index maycorrespond to a respective microsite. As shown in FIG. 22, entry 2200may include a name field 2210, a network address (NW ADDR) field 2220, atriggering criteria field 2230, a list of sensors field 2240, and ascore(s) field 2250.

Name field 2210 may store a descriptive name for a particular microsite.In some implementations, the descriptive name may be unique among themicrosites included in the index. As shown in FIG. 22, assume that entry2200 corresponds to the Rio Grand microsite from the example of FIG. 1.Name field 2210 may store the descriptive name “Rio” for the Rio Grandmicrosite.

Network address field 2220 may store a network address, such as a URL orURI, via which the particular microsite is available on a network, suchas network 1940. As shown in FIG. 22, network address field 2220 maystore the network address “rio.com” for the Rio Grand microsite.

Triggering criteria field 2230 may store triggering criteria thatidentify when the particular microsite will be identified as relevant.The triggering criteria may relate to various types of sensor data. Insome implementations, the triggering criteria may be stored in an N-arytree. As shown in FIG. 22, triggering criteria field 2230 may storetriggering criteria that specifies that the Rio Grand microsite isrelevant when a user is located within 50 meters of the restaurant ANDthe current time is between 11 AM and 11 PM AND . . . .

The triggering criteria may be specified as a Boolean expression. Assumethat the triggering criteria, for the particular microsite, includecriterion A and criterion B. In this case, for example, the triggeringcriteria may be specified as criterion A AND criterion B, or ascriterion A OR criterion B. The Boolean expression may include operatorsother than AND and OR.

In some implementations, indexing module 2120 may order the triggeringcriteria to place the criterion that is least likely to be satisfied,from among the triggering criteria, first. As one example, assume thatthe triggering criteria include criterion A—the time is between 6 AM and8 PM—AND criterion B—a user is located within 10 meters of a bus stop.In this case, indexing module 2120 may order the triggering criteria ascriterion B AND criterion A, because criterion B is least often to besatisfied between criterion A and criterion B. As another example,assume that the triggering criteria include criterion A—the time isbetween 6 AM and 8 PM—AND criterion B—a user is located within 10 metersof a bus stop—OR criterion C—the user is located within 25 meters of atrain stop. In this case, indexing module 2120 may order the triggeringcriteria as (criterion B or criterion C) AND criterion A, becausecriterion B and criterion C are least likely to be satisfied amongcriterion A, criterion B, and criterion C.

By placing the least likely criterion, or criteria, first in the Booleanexpression, it may be determined whether to exclude the particularmicrosite from consideration without having to test every criterion inthe triggering criteria. Returning to the example above with thetriggering criteria of criterion B AND criterion A, the particularmicrosite may be excluded from further consideration when criterion B isnot satisfied regardless of whether criterion A is satisfied. Returningto the example above with the triggering criteria of (criterion B orcriterion C) AND criterion A, the particular microsite may be excludedfrom further consideration when criterion B and criterion C are notsatisfied regardless of whether criterion A is satisfied. This may helpreduce the set of microsites, in the index, considered for presentationto a user device 1910.

List of sensors field 2240 may store information identifying a list ofsensors that is relevant to the particular microsite. The list ofsensors may identify sensors that output sensor data that is relevant tothe triggering criteria in triggering criteria field 2230 and/or sensordata that is relevant to the generation of the content of the particularmicrosite that will be presented on a user device 1910. As shown in FIG.22, list of sensors field 2240 may indicate that sensors relating tolocation, time, etc. are relevant to the Rio Grand microsite.

Score(s) field 2250 may store information regarding one or more scoresgenerated for the particular microsite, such as a popularity score, apersonalization score, and/or a social score. Other types of scores mayadditionally, or alternatively, be generated. One or more techniques,for generating the score(s) stored in score(s) field 2250, will bedescribed below.

The popularity score may be generated based on popularity dataassociated with the particular microsite. The personalization score maybe generated based on personalization data specific to a particular userrelative to the particular microsite. Score(s) field 2250 may store arespective personalization score for each of multiple users with apersonalization score, for the particular microsite, that satisfies apersonalization threshold. The social score may be generated based onsocial data specific to one or more social contacts, associated with aparticular user, for the particular microsite. Score(s) field 2250 maystore a respective social score for each of multiple users with a socialscore, for the particular microsite, that satisfies a social threshold.It may be possible for score(s) field 2250 to store, for the same user,a personalization score and a social score. The personalization score,in this situation, may be used when presenting information regarding theparticular microsite to the user. The social score, in this situation,may be used when presenting information regarding the particularmicrosite to another user for which the user is a social contact.

While FIG. 22 shows entry 2200 of the index as including particularfields, in some implementations, entry 2200 may include additionalfields, fewer fields, or different fields than are shown in FIG. 22.

Returning to FIG. 21, ranking module 2130 may receive user profile dataand sensor data from a user device 1910. Ranking module 2130 may use theuser profile data and/or the sensor data to identify relevantmicrosites. Ranking module 2130 may generate scores for the relevantmicrosites and present information regarding one or more of the relevantmicrosites, to user device 1910, based on the scores.

FIG. 23 is a diagram of example functional components of ranking module2130. As shown in FIG. 23, ranking module 2130 may include micrositeselection module 2310, microsite ranking module 2320, and micrositepresentation module 2330.

Microsite selection module 2310 may receive the sensor data and userprofile data associated with a user device 1910 and use the triggeringcriteria, in the index, to identify relevant microsites. In someimplementations, microsite selection module 2310 may identify micrositesthat are relevant based on the sensor data and the triggering criteria.For example, microsite selection module 2310 may perform a matching ofthe sensor data to the triggering criteria. In some implementations,microsite selection module 2310 may identify microsites that arerelevant based on the sensor data, the user profile data, and thetriggering criteria. For example, microsite selection module 2310 mayperform a matching of the sensor data and the user profile data to thetriggering criteria.

In either situation, as described above, the triggering criteria may berepresented as a Boolean expression. Microsite selection module 2310 mayanalyze as many of the triggering criteria, as necessary, to determinewhether a microsite is relevant. For example, if the triggering criteriainclude criterion A AND criterion B, microsite selection module 2310 maydetermine that microsites, which do not satisfy criterion A, are notrelevant microsites. As another example, if the triggering criteriainclude criterion A AND criterion B, microsite selection module 2310 maydetermine that microsites, which satisfy criterion A but do not satisfycriterion B, are not relevant microsites.

Microsite ranking module 2320 may generate scores for the relevantmicrosites and create a ranked list of microsites based on the scores.In some implementations, microsite ranking module 2320 may perform amatching of the sensor data to the triggering criteria, for a relevantmicrosite, to generate an index score for the relevant microsite. Insome implementations, microsite ranking module 2320 may perform amatching of the sensor data and the user profile data to the triggeringcriteria, for a relevant microsite, to generate an index score for therelevant microsite. In either situation, microsite ranking module 2320may compare the sensor data and/or the user profile data to eachcriterion, of the triggering criteria, and generate a real value thatrepresents a result of the comparison. Microsite ranking module 2320 maycombine the real values to generate the index score for the relevantmicrosite.

FIGS. 24A-24C are examples of functions that may be used to generatereal values based on matching sensor data and/or user profile data totriggering criteria. FIG. 24A illustrates a linear ascendant function.The linear ascendant function generates a real value as a result ofmatching sensor data and/or user profile data, x, relative to twocriterion variables, a and b. The two criterion variables, a and b, mayrepresent any of a number of attributes, such as time, distance,weather, etc. As shown in FIG. 24A, the real value may be zero when x<a;one when x>b; and (x−a)/(b−a) when a≤x≤b. Assume that a criterionstates: a user is within 50 meters of home. In this case, a=0 and b=50.The linear ascendant function may generate a real value based on wherethe user is located, x, relative to a and b.

FIG. 24B illustrates a quadratic ascendant function. The quadraticascendant function generates a real value as a result of matching sensordata and/or user profile data, x, relative to two criterion variables, aand b. As described above, the two criterion variables, a and b, mayrepresent any of a number of attributes, such as time, distance,weather, etc. As shown in FIG. 24B, the real value may be zero when x<a;one when x>b; and ((x−a)/(b−a))² when a≤x≤b. Assume that a criterionstates: a user is within 50 meters of home. In this case, a=0 and b=50.The quadratic ascendant function may generate a real value based onwhere the user is located, x, relative to a and b.

FIG. 24C illustrates a quadratic parabola function. The quadraticparabola function generates a real value as a result of matching sensordata and/or user profile data, x, relative to two criterion variables, aand b. As described above, the two criterion variables, a and b, mayrepresent any of a number of attributes, such as time, distance,weather, etc. As shown in FIG. 24C, the real value may be zero when x<a;zero when x>b; and 1−((x−(a+b)/2)²/(b−a)) when a≤x≤b. Assume that acriterion states: a user is within 50 meters of home. In this case, a=0and b=50. The quadratic parabola function may generate a real valuebased on where the user is located, x, relative to a and b.

While examples of functions are illustrated in FIGS. 24A-24C, otherfunctions are possible instead of the linear ascendant, quadraticascendant, and quadratic parabola functions.

Returning to FIG. 23, microsite ranking module 2320 may generate theindex score for a relevant microsite by combining the real values. Insome implementations, microsite ranking module 2320 may calculate theindex score as a sum, or some other combination, of the real values. Insome example implementations, each criterion, of the triggeringcriteria, may contribute equally to the index score. In some exampleimplementations, each criterion, of the triggering criteria, may beassigned a weight so that one criterion may contribute more to the indexscore than another criterion.

In some implementations, microsite ranking module 2320 may use the indexscores of the relevant microsites, as the total scores described below,to rank the relevant microsites in the ranked list of microsites. Insome implementations, microsite ranking module 2320 may modify the indexscores with one or more other scores, such as a popularity score, apersonalization score, and/or a social score, to generate total scoresfor the relevant microsites and rank the relevant microsites, in theranked list of microsites, based on the total scores.

In some implementations, as described above, microsite ranking module2320 may modify the score, of a microsite, based on a popularity scoreof the microsite. The popularity score of a microsite may be generatedbased on user behavior data associated with the microsite, such as howmany users expressed disinterest in the microsite by, for example,swiping away from the microsite or providing a negative rating when themicrosite was presented to a user device 1910, and/or how many usersexpressed interest in the microsite by, for example, providing apositive rating when the microsite was presented to a user device 1910,requesting additional information regarding the microsite, or purchasinga service or product associated with the microsite. In someimplementations, the popularity score of a microsite may be generatedusing one or more factors instead of, or in addition to, the userbehavior data, such as a quantity of times that the microsite has beenpresented to user devices 1910, an age of the microsite, a prior rankingor score of the microsite, or the like.

The popularity score, for a particular microsite, may be based onmultiple factors. A popularity factor score may be calculated for eachof the factors and these popularity factor scores may be combined toform the popularity score. In some example implementations, each of thepopularity factor scores may contribute equally to the popularity score.In some example implementations, each of the popularity factor scoresmay be assigned a weight, such that one of the popularity factor scoresmay contribute more to the popularity score than another one of thepopularity factor scores. A weight associated with a popularity factorscore, corresponding to a particular popularity factor, may depend onhow well the particular popularity factor is indicative of measuring thepopularity of a microsite.

Additionally, or alternatively, microsite ranking module 2320 may modifythe score, of a microsite, based on a personalization score of themicrosite. In some implementations, the personalization score of amicrosite may be generated based on the user profile data, such as useractivity data, associated with a user of a particular user device 1910,with regard to the microsite. The user activity data may include, forexample, whether the user has expressed disinterest in the microsite by,for example, swiping away from the microsite or providing a negativerating when the microsite was presented to the particular user device1910, and/or whether the user expressed interest in the microsite by,for example, providing a positive rating when the microsite waspresented to the particular user device 1910, requesting additionalinformation regarding the microsite, purchasing a service or productassociated with the microsite, bookmarking—e.g., saving—the microsite,orienting the particular user device 1910 to view the microsite withoutswiping away from the microsite, and/or following a recommendationprovided by the microsite—e.g., a recommendation to visit a particularrestaurant, see a particular movie, ride a particular bus, or the like.In some implementations, the personalization score of a microsite may begenerated using one or more factors instead of, or in addition to, theuser profile data, such as whether the user has recommended themicrosite to one of the user's social contacts.

The personalization score, for a particular microsite, may be based onmultiple factors. A personalization factor score may be calculated foreach of the factors and these personalization factor scores may becombined to form the personalization score. In some exampleimplementations, each of the personalization factor scores maycontribute equally to the personalization score. In some exampleimplementations, each of the personalization factor scores may beassigned a weight, or multiple weights, such that one of thepersonalization factor scores may contribute more to the personalizationscore than another one of the personalization factor scores. A weightassociated with a personalization factor score, corresponding to aparticular personalization factor, may depend on how well the particularpersonalization factor is indicative of measuring a user's interest in amicro site.

Additionally, or alternatively, microsite ranking module 2320 may modifythe score, of a microsite, based on a social score of the microsite. Insome implementations, the social score of a microsite may be generatedbased on friend activity data, associated with social contacts—e.g.,friends—of the user of a particular user device 1910, with regard to themicrosite. The user's friends may be identified based on the user'scommunications, the user's address book, and/or the user's account onone or more social networks. Examples of friend activity data,associated with a microsite, include whether the user's friends haveexpressed disinterest in the microsite by, for example, swiping awayfrom the microsite or providing a negative rating when the microsite waspresented to the friends' user devices 1910, and/or whether the user'sfriends expressed interest in the microsite by, for example, providing apositive rating when the microsite was presented to the friends' userdevices 1910, requesting additional information regarding the microsite,purchasing a service or product associated with the microsite,bookmarking the microsite, and/or following a recommendation provided bythe microsite—e.g., a recommendation to visit a particular restaurant,see a particular movie, ride a particular bus, or the like. In someimplementations, the social score of a microsite may be generated usingone or more factors instead of, or in addition to, the friend activitydata, such as whether the friends have recommended the microsite toothers.

In some implementations, the friend activity data may correspond to thesame data included in the user activity data. In some implementations,the friend activity data may include a subset—less than all—of the useractivity data. For example, the friend activity data may include thatdata, of the user activity data, that can be anonymized—i.e., nottraceable to a particular social contact. For example, the friendactivity data may include information regarding ratings of micrositesgiven by social contacts, and may not include information contained incommunications of the social contacts. In some example implementations,particular friend activity data may be used only when the same friendactivity data is available from at least a threshold quantity of socialcontacts. In some example implementations, particular friend activitydata, associated with a particular social contact, may be used only withthe express permission of the particular social contact.

In some implementations, the social score, for a particular user and aparticular microsite, may be based on friend activity data of multiplesocial contacts. A social contact score may be calculated for each ofthe social contacts and these social contact scores may be combined toform the social score. In some example implementations, each of thesocial contact scores may contribute equally to the social score. Insome example implementations, each of the social contact scores may beassigned a weight, such that one of the social contact scores maycontribute more to the social score than another one of the socialcontact scores. A weight associated with a social contact score,corresponding to a particular social contact, may depend on how close ofa friend the particular social contact is to the particular user. Thismay be determined in a number of different ways, such as whether theparticular social contact is in an address book of the particular user,whether the particular user has friended the particular social contactin a social network, the quantity of social networks that the particularuser has friended the particular social contact, the quantity ofcommunications that the particular user has had with the particularsocial contact, the frequency of communications that the particular userhas had with the particular social contact, or the like.

In some implementations, as described above, microsite ranking module2320 may generate a total score for a relevant microsite based on acombination of the index score and the popularity score, thepersonalization score, and/or the social score. In some implementations,microsite ranking module 2320 may generate a total score for a relevantmicrosite based on a combination of the index score, the popularityscore, the personalization score, and the social score. For example,microsite ranking module 2320 may add the popularity score, thepersonalization score, and/or the social score to the index score;multiply the index score by the popularity score, the personalizationscore, and/or the social score; boost the index score based on thepopularity score, the personalization score, and/or the social score; orcombine the index score with the popularity score, the personalizationscore, and/or the social score using a combination of these and/or otherways of combining the index score with the popularity score, thepersonalization score, and/or the social score.

In some implementations, microsite ranking module 2320 may generate atotal score for a microsite based on a weighted combination of the indexscore, the popularity score, the personalization score, and the socialscore. For example, microsite ranking module 2320 may assign a weight tothe index score, the popularity score, the personalization score, and/orthe social score. The weights may differ—in other words, the amount thateach of the index score, the popularity score, the personalizationscore, and the social score contributes to the total score may vary.Microsite ranking module 2320 may combine the weighted index score, theweighted popularity score, the weighted personalization score, and/orthe weighted social score to generate the total score.

Microsite ranking module 2320 may generate a ranked list of micrositesbased on the total scores. For example, microsite ranking module 2320may sort the relevant microsites based on the total scores for therelevant microsites. In some implementations, microsite ranking module2320 may rank a relevant microsite, with a higher total score, closer toa top of the ranked list than another relevant microsite, with a lowertotal score. In some implementations, microsite ranking module 2320 mayrank a relevant microsite, with a higher total score, closer to a bottomof the ranked list than another relevant microsite, with a lower totalscore.

Microsite presentation module 2330 may select a set of microsites fromthe ranked list of microsites and provide microsite information,regarding the set of microsites, to user device 1910. In someimplementations, microsite presentation module 2330 may select a set ofmicrosites based on the total scores. For example, micrositepresentation module 2330 may select the top scoring X microsites (X≥1).In some implementations, microsite presentation module 2330 may selectonly the top scoring microsite (X=1). In some implementations, micrositepresentation module 2330 may select the top scoring five (5) microsites(X=5). Rather than simply selecting the top scoring X microsites, insome implementations, microsite presentation module 2330 may select atop scoring microsite only when the total score, for the top scoringmicrosite, satisfies a score threshold.

Microsite presentation module 2330 may provide information, regardingthe set of microsites, to user device 1910. In some implementations, theinformation may include a network address and/or a list of sensors foreach microsite in the set of microsites. In some implementations, thenetwork addresses of the microsites may be provided in a ranked listbased on the total scores of the microsites. In some implementations,the network addresses of the microsites may be provided along with thetotal scores of the microsites.

While FIG. 23 shows a particular quantity and arrangement of modules, insome implementations, ranking module 2130 may include fewer modules,additional modules, different modules, or differently arranged modules.

FIG. 25 is a flowchart of an example process 2500 for presenting contentof a microsite. In some implementations, process 2500 may be performedby user device 1910. In some implementations, one or more blocks ofprocess 2500 may be performed by one or more devices instead of, orpossibly in conjunction with, user device 1910.

Process 2500 may include receiving user profile data (block 2510). Forexample, user profile module 2020, of user device 1910, may receive andstore user profile data associated with user device 1910 and/or a userof user device 1910. User profile module 2020 may receive user profiledata from the user and/or may receive user profile data from one or moreother components or programs of user device 1910. Examples of userprofile data have been identified above. User profile module 2020 mayprovide the user profile data to application module 2010.

Process 2500 may include receiving sensor data (block 2520). Forexample, sensors module 2030, of user device 1910, may receive and storesensor data associated with user device 1910. Sensors module 2030 mayreceive sensor data from one or more components of user device 1910and/or may receive sensor data from one or more devices external to userdevice 1910, such as one or more servers 1930 and/or one or more otheruser devices 1910. Examples of sensor data have been identified above.Sensors module 2030 may provide the sensor data to application module2010.

Process 2500 may include providing the user profile data and the sensordata to ranking system 1920 (block 2530). In some implementations,application module 2010, of user device 1910, may periodically orregularly provide the user profile data and the sensor data to rankingsystem 1920. Application module 2010 may provide the user profile dataand the sensor data to ranking system 1920 automatically—e.g., withoutuser input.

As described above, ranking system 1920 may receive the user profiledata and the sensor data from user device 1910. Ranking system 1920 mayuse the user profile data and/or the sensor data to identify a set ofrelevant micro sites. Ranking system 1920 may compare the user profiledata and/or the sensor data to the triggering criteria for a micrositeand generate a score for the microsite based on a result of thecomparison. As described above, ranking system 1920 may modify the scorebased on one or more factors, such as a popularity score, apersonalization score, and/or a social score. Ranking system 1920 mayselect a set of microsites based on their scores and provideinformation, regarding the set of microsites, to user device 1910.

Process 2500 may include receiving information regarding a set ofmicrosites from ranking system 1920 (block 2540). For example,application module 2010, of user device 1910, may receive information,such as network addresses and lists of sensors, for the set ofmicrosites.

Process 2500 may include sending a request, for a microsite, with sensordata to a server 1930 (block 2550). For example, display module 2040may, for each microsite in the set of microsites, send a request to aserver 1930 that hosts the microsite. Display module 2040 may use thenetwork address, associated with the microsite, to send the request andprovide sensor data associated with the list of sensors that arerelevant to the microsite. In some implementations, as described above,the request may take the form of a GET request.

Process 2500 may include receiving microsite content from server 1930(block 2560). In response to sending the request and the sensor data toserver 1930, server 1930 may identify the microsite content to send touser device 1910. The microsite content may be dynamic in the sense thatthe content may change depending on the sensor data received from userdevice 1910. For example, if the microsite relates to an exercisemicrosite, server 1930 may receive information regarding the currentgeographic location, the current speed, and the current direction ofuser device 1910, and may generate the microsite content based on thisinformation. Server 1930 may send the microsite content to displaymodule 2040 of user device 1910. Display module 2040 may receive themicrosite content from server 1930.

Process 2500 may display the microsite content (block 2570). Forexample, display module 2040 may cause the microsite content to appearon a display associated with user device 1910. In some implementations,display module 2040 may determine whether it is an appropriate time todisplay the microsite content. For example, display module 2040 maydetermine whether user device 1910 has been idle for a particular amountof time and cause the microsite content to be displayed only if userdevice 1910 has been idle for at least the particular amount of time.Alternatively, or additionally, display module 2040 may determinewhether user device 1910 is in a lock mode and cause the micrositecontent to be displayed only if user device 1910 is in the lock mode.Alternatively, or additionally, display module 2040 may use anotherfactor to determine whether to cause the microsite content to bedisplayed.

While FIG. 25 shows process 2500 as including a particular quantity andarrangement of blocks, in some implementations, process 2500 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIG. 26 is a flowchart of example process 2600 for providing informationregarding a set of microsites. In some implementations, process 2600 maybe performed by ranking system 1920. In some implementations, one ormore blocks of process 2600 may be performed by one or more devicesinstead of, or possibly in conjunction with, ranking system 1920.

Process 2600 may include receiving microsite information (block 2610).For example, input module 2110, of ranking system 1920, may include orinteract with a crawler that locates microsites via a crawlingoperation. As described above, the microsites may be located based on apiece of code, located on the microsites, which identifies themicrosites as microsites. The microsites may be analyzed to identifyinformation regarding the microsites. Additionally, or alternatively,input module 2110 may receive information regarding microsites viamanual input via a user interface provided by input module 2110. In someimplementations, input module 2110 may receive or determine micrositeinformation, such as descriptive names of the microsites, networkaddresses associated with the microsites, triggering criteria thatspecify when the microsites may be identified for presentation, and/orlists of sensors that are relevant to the content of the microsites.

Process 2600 may include storing the microsite information in an index(block 2620). For example, indexing module 2120, of ranking system 1920,may store the microsite information in an index. For a particularmicrosite, indexing module 2120 may store a descriptive name for theparticular microsite, a network address for the particular microsite,triggering criteria for the particular microsite, and/or a list ofsensors for the particular microsite, as described above with regard toFIG. 22.

Process 2600 may include receiving user profile data and sensor datafrom user device 1910 (block 2630). For example, as described above,user device 1910 may automatically and periodically/regularly send userprofile data and sensor data to ranking system 1920. Ranking module2130, of ranking system 1920, may receive the user profile data and thesensor data from user device 1910.

Process 2600 may include searching the index, based on the triggeringcriteria and the user profile data and/or the sensor data, to identifyrelevant microsites (block 2640), and generating scores for the relevantmicrosites (block 2650). For example, ranking module 2130 may identifyrelevant microsites, in the index of indexing module 2120, based on theuser profile data and/or the sensor data, as described above. Rankingmodule 2130 may generate an index score for a relevant microsite basedon how well the user profile data and/or the sensor data matches thetriggering criteria for the relevant microsite. In some implementations,as described above, ranking module 2130 may modify the index score, forthe microsite, based on one or more scores, such as a popularity score,a personalization score, and/or a social score for the microsite, togenerate a total score for the microsite.

Process 2600 may include selecting one or more of the top-scoringmicrosites (block 2660) and providing information regarding the selectedtop-scoring microsite(s) (block 2670). For example, ranking module 2130may select a set of the relevant microsites based on their scores, suchas the top scoring X microsites. Ranking module 2130 may provideinformation, regarding the set of relevant microsites, to user device1910. In some implementations, as described above, the information mayinclude a network address and a list of sensors for each microsite inthe set of relevant microsites. User device 1910 may use the networkaddress, of a microsite, to retrieve the content of the microsite from aserver 1930.

While FIG. 26 shows process 2600 as including a particular quantity andarrangement of blocks, in some implementations, process 2600 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIG. 27 is a flowchart of an example process 1000 that may correspond toblock 2650 of process 2600 of FIG. 26. In some implementations, asdescribed above, process 1000 may be performed by ranking system 1920.In some implementations, one or more of blocks of process 1000 may beperformed by one or more devices instead of, or possibly in conjunctionwith, ranking system 1920.

Process 2700 may include selecting a microsite from the index (block2710). For example, ranking module 2130 may select one of the relevantmicrosites to analyze. The selection may be made in any manner, such asbased on name, network address, or the like.

Process 2700 may include generating an index score for the micrositebased on a match of the sensor data and/or the user profile data to themicrosite's triggering criteria (block 2720). In some implementations,ranking module 2130 may generate the index score based on a comparisonof the sensor data to the triggering criteria. In some implementations,ranking module 2130 may generate the index score based on a comparisonof the sensor data and the user profile data to the triggering criteria.

Process 2700 may include determining a popularity score, apersonalization score, and/or a social score associated with themicrosite (block 2730). In some implementations, ranking module 2130 maygenerate the popularity score, the personalization score, and/or thesocial score for the microsite using one or more of the factorsdescribed above. In some implementations, ranking module may determinethe popularity score, the personalization score, and/or the social scorefor the microsite by, for example, reading the popularity score, thepersonalization score, and/or the social score from an entry in theindex. In this situation, the popularity score, the personalizationscore, and/or the social score may be determined off-line and not inresponse to an analysis of a microsite.

Process 2700 may include modifying the index score of the micrositebased on the popularity score, the personalization score, and/or thesocial score to generate a total score (block 2740). In someimplementations, as described above, ranking module 2130 may use theindex score as the total score for the microsite. In someimplementations, ranking module 2130 may modify the index score togenerate the total score based on the popularity score, thepersonalization score, and/or the social score, as described above.

Process 2700 may include determining whether there are any moremicrosites to score (block 2750). If there are additional microsites toscore (block 2750—YES), then process 2700 may return to block 2710 toselect another microsite. If there are no additional microsites to score(block 2750—NO), then process 2700 may proceed to block 2660 in FIG. 26.Process 2700 may be repeated for each relevant microsite identified withregard to block 2640 in FIG. 26 until all relevant microsites have beenprocessed.

While FIG. 27 shows process 2700 as including a particular quantity andarrangement of blocks, in some implementations, process 2700 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel. Additionally, or alternatively, multiple instances of process2700 may be performed concurrently for different microsites.

FIG. 28 is a diagram of illustrating an example process flow 2800 thatinvolves user device 1910, ranking system 1920, and servers 1930. WhileFIG. 28 shows process flow 2800 as including a particular sequence ofinteractions among user device 1910, ranking system 1920, and servers1930, in some implementations, some of these interactions may occur inanother order and/or in parallel.

As shown at (A) in FIG. 28, input module 2110, of ranking system 1920,may identify microsites for use by ranking system 1920. In someimplementations, as described above, input module 2110 may identifymicrosites through crawling and/or via manual input. In eithersituation, input module 2110 may obtain information regarding aparticular microsite, such as a descriptive name of the particularmicrosite, a network address for the particular microsite, triggeringcriteria for the particular microsite, and/or a list of sensors that arerelevant for the particular microsite.

As shown at (B) in FIG. 28, input module 2110, of ranking system 1920,may provide information regarding various microsites to indexing module2120. Indexing module 2120 may store information regarding themicrosites in one or more indexes. In some implementations, as describedabove, indexing module 2120 may store, for a particular microsite in anindex, a descriptive name of the particular microsite, a network addressfor the particular microsite, triggering criteria for the particularmicrosite, and/or a list of sensors that are relevant for the particularmicrosite.

As shown at (C) in FIG. 28, application module 2010, of user device1910, may obtain user profile data from user profile module 2020 and/ormay obtain sensor data from sensors module 2030. The user profile datamay include various information regarding user device 1910 and/or a userof user device 1910. Examples of user profile data have been givenabove. The sensor data may include various information regarding userdevice 1910 and/or conditions associated with user device 1910. Examplesof sensor data have been given above.

As shown at (D) in FIG. 28, application module 2010 may provide the userprofile data and/or the sensor data to ranking system 1920. As describedabove, application module 2010 may automatically—e.g., without requiringan instruction from a user of user device 1910—provide the user profiledata and/or the sensor data to ranking system 1920. Ranking module 2130,of ranking system 1920, may receive the user profile data and/or thesensor data.

As shown at (E) in FIG. 28, ranking module 2130 may use the user profiledata and/or the sensor data to identify relevant microsites. Asdescribed above, in some implementations, ranking module 2130 mayidentify relevant microsites, in the index, based on the sensor data andthe triggering criteria, and generate an index score for the relevantmicrosites based on a result of a matching of the sensor data to thetriggering criteria. As also described above, in some implementations,ranking module 2130 may identify relevant microsites, in the index,based on the user profile data and the sensor data, and generate anindex score for the relevant microsites based on a result of a matchingof the user profile data and the sensor data to the triggering criteria.As described above, in some implementations, ranking module 2130 maymodify the index score, for a microsite, based on one or more otherscores to generate a total score for the microsite. Ranking module 2130may use the total score to identify a set of relevant microsites.

As shown at (F) in FIG. 28, ranking module 2130 may provide information,regarding the set of relevant microsites, to user device 1910. Asexplained above, in some implementations, the information may include,for each microsite in the set of relevant microsites, a network addressfor the microsite and a list of sensors relevant to the microsite.Application module 2010, of user device 1910, may receive theinformation regarding the set of relevant microsites.

As shown at (G) in FIG. 28, application module 2010 may provide theinformation, regarding the set of relevant microsites, to display module2040 of user device 1910. Display module 2040 may receive theinformation regarding the set of relevant microsites. Display module2040 may obtain sensor data associated with the list of sensors thathave been identified as relevant to the relevant microsites. For eachrelevant microsite, display module 2040 may generate a request thatincludes the network address for the relevant microsite and the sensordata relevant to the relevant microsite.

As shown at (H) in FIG. 28, display module 2040 may transmit therequests to one or more servers 1930. Whether display module 2040transmits the requests to more than one server 1930 depends on whichserver(s) 1930 is/are hosting the relevant microsites. In other words,all of the relevant microsites may be hosted by a single server 1930,all of the relevant microsites may be hosted by separate, differentservers 1930, or something in between these two extremes.

Server(s) 1930 may receive the requests from user device 1910 may obtaincontent of the relevant microsites. In some implementations, asdescribed above, the content of a relevant microsite may be dynamic inthe sense that the content of the relevant microsite is based on thesensor data received from user device 1910.

As shown at (I) in FIG. 28, server(s) 1930 may provide the content ofthe relevant microsites to user device 1910. Display module 2040, ofuser device 1910, may receive the content and present the content on adisplay associated with user device 1910. For example, display module2040 may push the content, for the relevant microsites, as a slidingdisplay of content. In some implementations, content for one of therelevant microsites may be presented on the display at a time. A user,of user device 1910, may interact with the content, using a finger orthe like, to express the user's interest or disinterest in the contentor to see the content for another one of the relevant microsites.

FIGS. 29-36 illustrate an example of identifying and presentingmicrosite content. As shown in FIG. 29, assume that a user (“Carly”) iswalking in town and takes, with her, a user device in the form of awatch. The watch sends user profile data and sensor data to the rankingsystem. As shown in FIG. 29, assume that the user profile data includesinformation identifying Carly's user profile—i.e., ABC123—which mayinclude any kind of identifier that the ranking system may use to locateCarly's user profile. The ranking system may obtain Carly's preferencesfrom her user profile. As further shown in FIG. 29, assume that thesensor data includes information identifying the current date—i.e., Mar.2, 2012; the current time—i.e., 11:32 AM; the current weathercondition—i.e., sunny; Carly's current speed—i.e., 0.8 kilometers perhour (KPH); and Carly's current geographic location—i.e., latitude (LAT)40.52202 and longitude (LONG) −79.84180.

As shown in FIG. 30, assume that the ranking system applies the sensordata to the triggering criteria, for the microsites in the index, toidentify a set of relevant microsites. For example, the ranking systemmay compare the sensor data to the triggering criteria, for each of themicrosites in the index, to identify which of the microsites arerelevant to the sensor data. As shown in FIG. 30, assume that theranking system identifies the following relevant microsites: a busnotifier microsite, an Action League microsite, a Calendar microsite, aRio Grand microsite, and a history microsite.

For the Action League microsite, assume that the index stores thefollowing triggering criteria: user is within 100 meters of a theatershowing the Action League movie AND the current time is within 60minutes of the movie start time AND the user is moving less than 5 KPH.The ranking system may determine that the Carly's sensor data satisfiesthe triggering criteria. For example, assume that Carly is currently 50meters from Regal Cinema which is showing the Action League movie, whichsatisfies the criterion that the user be within 100 meters of a theatershowing the Action League movie. Further assume that the movie starts in8 minutes, which satisfies the criterion that the current time be within60 minutes of the movie start time. Based on Carly's sensor data, Carlyis moving at 0.8 KPH, which satisfies the criterion that the user bemoving less than 5 KPH.

As shown in FIG. 31, assume that the ranking system applies the sensordata to the triggering criteria for the relevant microsites in the indexto generate index scores for the relevant microsites. For example, theranking system may compare the sensor data to the triggering criteria,for each of the relevant microsites, to generate the index scores. Asdescribed above, the ranking system may use a function, similar to thefunctions described with regard to FIGS. 24A-24C, to generate realvalues that may be used for the index scores.

For the Action League microsite, assume that the ranking system appliesCarly's sensor data to the triggering criteria and generates an indexscore of 0.9—on an example scale of zero to one. Assume further that theAction League microsite is the top-scoring microsite among the relevantmicrosites.

As shown in FIG. 32, the ranking system may determine a popularity scorefor a relevant microsite—shown as the Action League microsite in FIG.32. The ranking system may use various data, as described above.Examples of types of data, shown in FIG. 32, include user behavior datarelating to the Action League microsite; user rankings data relating tothe Action League microsite; microsite age data corresponding to the ageof the Action League microsite, and/or data reflecting the quantity oftimes that the Action League microsite has been presented to userdevices 1910. Assume that the user behavior data indicates that usershave previously followed a recommendation given by the Action Leaguemicrosite by going to see the movie; that the user rankings dataindicates that users have given the Action League microsites overallfavorable ratings; that the microsite age data indicates that the ActionLeague microsite is relatively new; and that the data reflecting thequantity of times that the microsite has been presented to user devices1910 indicates that the Action League microsite has been presented 1,000times. The ranking system may generate a popularity factor score foreach of these types of data and combine the popularity factor scores todetermine the popularity score for the Action League microsite.

As shown in FIG. 33, the ranking system may determine a personalizationscore for Carly relative to the Action League microsite. The rankingsystem may use various data, as described above. Examples of types ofdata, shown in FIG. 33, include search activity data corresponding toCarly's searches relating to the Action League movie; browsing activitydata corresponding to Carly browsing the web for information relating tothe Action League movie; communication activity data corresponding toCarly's communications involving the Action League movie; postingactivity data relating to Carly's postings on social networks, blogs, orother public sites relating to the Action League movie; and micrositeactivity data corresponding to Carly's prior interactions with theAction League microsite. Assume that the search activity data indicatesthat Carly has performed one or more web searches for the Action Leaguemovie; that the browsing activity data indicates that Carly has accesseda trailer for the Action League movie; that the communication activitydata indicates that Carly has sent two e-mails regarding the ActionLeague movie; that the posting activity data indicates that Carly hasposted a comment regarding the Action League movie on a social network;and that the microsite activity data indicates that Carly has notdismissed—e.g., swiped away—the Action League microsite when previouslypresented on Carly's watch. The ranking system may generate apersonalization factor score for each of these types of data and combinethe personalization factor scores to determine the personalization scorefor Carly relative to the Action League microsite.

As shown in FIG. 34, the ranking system may determine a social score forCarly's social contacts relative to the Action League microsite. Theranking system may use various data, as described above. Examples oftypes of data, shown in FIG. 34, include search activity datacorresponding to Carly's social contacts' searches relating to theAction League movie; posting activity data relating to Carly's socialcontacts' postings on social networks, blogs, or other public sitesrelating to the Action League movie; and microsite activity datacorresponding to Carly's social contacts' prior interactions with theAction League microsite. Assume that the search activity data indicatesthat Carly's social contacts have performed web searches for the ActionLeague movie; that the posting activity data indicates that Carly'ssocial contacts have posted several comments regarding the Action Leaguemovie on social networks; and that the microsite activity data indicatesthat Carly's social contacts have provided favorable ratings to theAction League microsite when previously presented to user devices ofCarly's social contacts. The ranking system may generate a social factorscore for each of these types of data and combine the social factorscores to determine the social score for Carly's social contactsrelative to the Action League microsite.

As shown in FIG. 35, the ranking system may input the index score, thepopularity score, the personalization score, and the social score into ascoring function. The scoring function may be a simple summation ofthese scores or something more complex. For example, the ranking systemmay assign weights to the different scores and combine the weightedscores using the scoring function to obtain a total score.

As shown in FIG. 36, assume that the ranking system selects thetop-scoring Action League microsite for presentation to Carly's watch.The ranking system may provide information regarding the Action Leaguemicrosite to Carly's watch. As shown in FIG. 36, the ranking system mayprovide a network address for the Action League microsite—shown asalm.com/micro—and a list of sensors for the Action Leaguemicrosite—shown as time and location. Carly's watch may receive thenetwork address and list of sensors and determine sensor data relatingto the sensors on the list. Carly's watch may use the network address toaccess the Action League server and send the sensor data to the ActionLeague server. The Action League server may generate or modify thecontent of the Action League microsite based on the sensor data andprovide the content for presentation on a display of Carly's watch. Asshown in FIG. 36, Carly's watch may display information that the ActionLeague movie starts in 8 minutes at the Regal Cinema, which is just twoblocks from Carly's current location.

A system and method, described herein, may determine a relevantmicrosite to provide to a user device based on context data without theneed for a user, of the user device, to request the microsite. Themicrosite may provide information that may be useful to the user.

Example 4

A system and/or method, as described herein, may provide relevantmicrosites to a user device based on context data and without the needfor a user, of the user device, to request the microsites. The contextdata may include user profile data relating to the user or the userdevice and/or sensor data relating to one or more conditions associatedwith the user device. In some implementations, the relevant micrositesthat are provided or the order in which the relevant microsites areprovided to the user device may be based on whether the user haspreviously purchased any of the relevant microsites. The microsites mayprovide information that may be useful to the user.

FIGS. 37A-37D are diagrams illustrating an overview 3700 of an exampleimplementation described herein. With reference to FIG. 37A, assume auser, of a user device, accesses a microsite store, which providesmicrosites for purchase. Assume that the user has identified amicrosite, named “Music ID,” that the user desires to purchase. Thus, asshown in FIG. 37A, the user may select a BUY button to begin purchase ofthe microsite. Thereafter, the user's device may provide paymentinformation for completing the purchase of the microsite.

Upon purchase of the microsite, the user may be presented with a list oftriggering criteria that dictate when the purchased microsite will beprovided to the user's device, as shown in FIG. 37B. The user may acceptor edit the triggering criteria. Upon acceptance of theoriginally-presented triggering criteria or an edited version of thetriggering criteria, the user's device may store, in a user profile,information relating to the purchased microsite, such as informationidentifying the microsite and possibly the triggering criteria. Assume,for example 3700, that the user accepts the original triggeringcriteria, which indicate that the Music ID microsite will be presentedto the user's device when the user is at home, the time is not between11 PM and 7 AM, and music is playing.

From time to time, the user's device may transmit, with the user'spermission, sensor data to a ranking system. In addition, the user'sdevice may transmit, with the user's permission, user profile data tothe ranking system. Assume, at some point in time, the user's devicetransmits, as shown in FIG. 37C, sensor data, to the ranking system,that indicates that the current geographic location of the user's devicecorresponds to the user's home, that the time is 9 PM, and that musichas been detected. In addition, the user's device may transmit, to theranking system, information identifying microsites that have beenpurchased by the user. Thus, in example 3700, the user's device maytransmit, to the ranking system, information identifying the Music IDmicrosite.

Based on the sensor data, assume that the ranking system identifies agroup of microsites that are relevant to the sensor data. Since thesensor data satisfies the triggering criteria for the Music IDmicrosite, assume that the group of microsites includes the Music IDmicrosite. In addition, based on the information identifying micrositesthat have been purchased by the user, the ranking system may identifythe Music ID microsite as the one that is to be provided to the user'sdevice before the other microsites in the identified group. As a result,the ranking system may provide, to the user's device, an address foraccessing the Music ID microsite, as illustrated in FIG. 37C.

The user's device may use the address to obtain the Music ID micrositefrom, for example, a server that hosts the microsite. As part ofobtaining the microsite, the user's device may send an audio clip,containing a portion of the music detected by the user's device, to theserver. The server may use the audio clip to identify the song andartist. The Music ID microsite may be presented to the user via theuser's device, as shown in FIG. 37D. As shown, the Music ID micrositemay present the name of the song that is currently playing in the user'shome and the name of the artist of the song. Thus, a purchased micrositethat is determined to be relevant to sensor data, received from a user'sdevice, may be provided before other relevant microsites that have notbeen purchased.

FIG. 38 is a diagram of an example environment 3800 in which systemsand/or methods described herein may be implemented. Environment 3800 mayinclude a group of user devices 3810 connected to a ranking system 3820,and multiple servers 3830-1 through 3830-N (where N>1) (referred tocollectively as “servers 3830” and, at times, individually, as “server3830”) via a network 3840.

User device 3810 may include a client device, or a collection of clientdevices, that is capable of presenting a document on a display. Examplesof user device 3810 may include a smart phone, a personal digitalassistant, a laptop, a tablet computer, a camera, a watch, a personalcomputer, and/or another type of device with the ability to display amicrosite. In some implementations, user device 3810 may include abrowser via which a microsite may be presented on a display associatedwith user device 3810.

Ranking system 3820 may include a server device or a collection ofserver devices which may be co-located or remotely located. Rankingsystem 3820 may identify microsites and index information associatedwith the microsites. Ranking system 3820 may identify relevantmicrosites to present to a user device 3810, based on, for example,context data received from user device 3810 and triggering criteria fortriggering the presentation of the microsites, and provide informationregarding the relevant microsites to user device 3810. In addition,ranking system 3820 may provide one or more user interfaces, to userdevice 3810, to allow a user, of user device 3810, to purchase amicrosite.

Server 3830 may include a server device or a collection of serverdevices that may be co-located or remotely located. Any two or more ofservers 3830 may be implemented within a single, common server device ora single, common collection of server devices. Servers 3830 may hostdocuments, such as microsites. In some implementations, one or more ofservers 3830 may be affiliated with a same entity (e.g., party,organization, business, company, etc.) as ranking system 3820. In someimplementations, none of servers 3830 may be affiliated with the sameentity as ranking system 3820.

While ranking system 3820 is shown as separate from servers 3830, it maybe possible for ranking system 3820 to perform one or more of thefunctions described as being performed by a server 3830 and/or a server3830 to perform one or more of the functions described as beingperformed by ranking system 3820. For example, ranking system 3820 mayhost some or all of the microsites. Additionally, or alternatively, auser device 3810 may host some of the microsites and/or may perform oneor more of the functions of ranking system 3820.

Network 3840 may include any type of network, such as, for example, alocal area network (“LAN”), a wide area network (“WAN”), a telephonenetwork, such as the Public Switched Telephone Network (“PSTN”) or acellular network, an intranet, the Internet, or a combination of theseor other types of networks. User device 3810, ranking system 3820, andservers 3830 may connect to network 3840 via wired and/or wirelessconnections. In other words, any one of user device 3810, ranking system3820, and/or servers 3830 may connect to network 3840 via a wiredconnection, a wireless connection, or a combination of a wiredconnection and a wireless connection.

Although FIG. 38 shows example components of environment 3800, in someimplementations, environment 3800 may include additional components,fewer components, different components, or differently arrangedcomponents than those depicted in FIG. 38. Additionally, oralternatively, one or more components of environment 3800 may performone or more tasks described as being performed by one or more othercomponents of environment 3800.

FIG. 39 is a diagram of example functional components of user device3810. In some implementations, the functional components, shown in FIG.39, may be implemented by user device 3810. In some implementations, oneor more of the functional components, shown in FIG. 39, may beimplemented by a device separate from user device 3810, such as anotheruser device 3810 operating in combination with user device 3810.

As shown in FIG. 39, user device 3810 may include an applicationcomponent 3910, a user profile component 3920, a sensors component 3930,and a display component 3940. Application component 3910 may control theoperation of user device 3810 with regard to the presentation ofmicrosites on user device 3810. In some implementations, applicationcomponent 3910 may take the form of a browser application. In someimplementations, application component 3910 may automatically run whenuser device 3810 powers on or boots up, or may run when instructed by auser of user device 3810. In some implementations, application component3910 may run in the background on user device 3810. The user, of userdevice 3810, may stop application component 3910 from running at anytime.

Application component 3910 may allow a user, of user device 3810, topurchase a microsite. For example, application component 3910 may accessan online store, provided by ranking system 3820 or anothersystem/device, that provides microsites for purchase. Applicationcomponent 3910 may receive information identifying microsite contentthat the user desires to purchase, may provide monetary payment—e.g., inthe form of credit card information—to ranking system 3820 and/oranother system/device, and may store information relating to themicrosite in user profile component 3920.

Application component 3910 may obtain information from user profilecomponent 3920 and sensors component 3930 and provide the information toranking system 3820. Application component 3910 may also receiveinformation regarding one or more microsites from ranking system 3820.In some implementations, the information, regarding a microsite, mayinclude a network address, such as a URL or URI, associated with themicrosite from ranking system 3820. Additionally, or alternatively, theinformation, regarding a microsite, may include a list of sensors thatis relevant to the content of the microsite. Application component 3910may provide the information to display component 3940. In someimplementations, application component 3910 may automatically obtaininformation from user profile component 3920 and/or sensors component3930, and/or automatically provide the information to ranking system3820—e.g., without input from a user of user device 3810. In someimplementations, application component 3910 may periodically provide theinformation to ranking system 3820—e.g., according to no predefinedschedule. In some implementations, application component 3910 mayregularly provide the information to ranking system 3820—e.g., accordingto a predefined schedule. In some implementations, application component3910 may provide the information to ranking system 3820 based on aschedule identified by the user of user device 3810—e.g., every 5minutes between 10 AM and 11 PM when user device 3810 has been idle forat least 5 minutes but not when user device 3810 is charging. In someimplementations, application component 3910 may provide the informationto ranking system 3820 according to some other criteria.

User profile component 3920 may obtain, store, and/or provide userprofile data. User profile data may include various informationregarding user device 3810, a user of user device 3810, and/or one ormore other user devices 3810 associated with the user of user device3810. The user profile data may only be obtained, stored, and/orprovided with the user's express permission, and the user profile datamay be anonymized with regard to the identity of the user. In someimplementations, user profile component 3920 may store some user profiledata and an identifier associated with additional user profile data,which may be stored externally to user device 3810, such as at rankingsystem 3820 or at a server accessible by ranking system 3820. In someimplementations, user profile component 3920 may simply store anidentifier associated with the user profile data, which may be storedexternally to user device 3810, such as at ranking system 3820 or at aserver accessible by ranking system 3820. Thus, references, herein, touser profile data may refer to an identifier associated with the userprofile data.

Examples of user profile data may include information identifying amicrosite that has been purchased via user device 3810; informationidentifying a date on which a microsite was purchased; informationidentifying a time at which the microsite was purchased; user-modifiedtriggering criteria for a purchased microsite; rankings for purchasedmicrosites; geographic addresses associated with the user, such as theaddress of the user's home, the address of the user's place of business,the address of a location frequented by the user, etc.; informationinputted into a calendar associated with the user; information regardingthe user's interaction with microsites that have been presented to theuser, such as ratings given to the microsites, whether the user hasdismissed—e.g., swiped away—from microsites that have been presented tothe user, or the like; information regarding the user's communications,such as e-mails, text messages, instant messages, voicemail messages, orthe like; information regarding the user's activity on the web, such asinformation regarding the user's searches, the user's browsing activity,the user's posts on social networks, blogs, and/or other public websites; information regarding activities on the web of the user's socialcontacts, such as people with which the user has communicated, or otherpeople having a social relationship with the user, names and/oridentifiers—e.g., identifiers that are anonymized with regard to theidentities of particular individuals—of people listed in the user'saddress book, people friended by the user on social networks or otherpublic web sites; and/or information regarding the user's habits, suchas places that the user has visited, things that the user has done, atwhat time the user usually gets up in the morning, or the like. Whilecertain examples of user profile data have been identified above, othertypes of user profile data are possible.

The user may review, add, remove, and/or revise the user profile data atany time. In some implementations, the user may specify what type ofinformation is to be used for the user profile data. For example, theuser may specify that the information regarding the user's activity onthe web is to be used for the user profile data, and the informationregarding the user's communications and the information regarding theuser's friends' activities on the web are not to be used for userprofile data.

Sensors component 3930 may obtain, store, and/or provide sensor data.Sensor data may include various information regarding user device 3810and/or conditions associated with user device 3810. The sensor data mayonly be obtained, stored, and/or provided with the user's expresspermission, and the sensor data may be anonymized with regard to theidentity of the user. Sensor component 3930 may interact with one ormore components of user device 3810, such as an accelerometer, a globalpositioning system component, a communication component, or the like, toobtain the sensor data. Additionally, or alternatively, sensor component3930 may interact with one or more external devices, such as one or moreservers, to obtain the sensor data.

Examples of sensor data may include information regarding a currentgeographic location of user device 3810; information regarding soundsoccurring at or around user device 3810; information regarding currentlighting condition at user device 3810; information regarding a currentdate and/or time associated with user device 3810; information regardinga current speed of user device 3810; information regarding a currentdirection in which user device 3810 is moving; information regarding acurrent orientation or change in orientation of user device 3810;information regarding a current weather condition in the location inwhich user device 3810 is located; information regarding a currenttemperature in the location in which user device 3810 is located; and/orinformation regarding interaction of user device 3810 with other deviceswith which user device 3810 is in communication. While certain examplesof sensor data have been identified above, other types of sensor dataare possible.

The user may specify what type of information is to be used for thesensor data. For example, the user may specify that the currentgeographic location, the current time, the current speed, the currentdirection, and the current orientation or change in orientation of userdevice 3810 are to be used for the sensor data, and the interaction ofuser device 3810 with other devices is not to be used for the sensordata.

Display component 3940 may receive information, such as a networkaddress associated with a microsite and/or a list of sensors that arerelevant to the microsite, from application component 3910. Displaycomponent 3940 may use the information to transmit a request to a server3830 to obtain the microsite. The request may include the networkaddress, associated with the microsite, and sensor data associated withthe sensors in the list. The sensor data, included with the request, maybe a subset of the sensor data obtained by sensors component 3930. Insome particular implementations, the request may include a GET requestand the content of the microsite may include hypertext mark-up language(HTML), cascading style sheets (CSS), or Javascript.

Display component 3940 may receive the microsite and render the contentof the microsite on a display associated with user device 3810. In someimplementations, the content of the microsite may include code to obtainreal-time sensor data from user device 3810 or a device separate fromuser device 3810. In some example implementations, this code may obtainthe real-time sensor data once when the content of the microsite isrendered on the display. In some example implementations, this code mayobtain the real-time sensor data more than once while the content of themicrosite is rendered on the display. The content of the microsite maybe updated based on the real-time sensor data.

In some implementations, display component 3940 may push the content tothe display so as to override any content already on the display. Insome implementations, display component 3940 may determine anappropriate time to render the content of the microsite, such as whenuser device 3810 is idle for a particular amount of time, when userdevice 3810 is in a lock mode, when user device 3810 is in a particularorientation, or the like. In some implementations, a user of user device3810 may specify how and when the user will be presented with thecontent of a microsite. For example, the user may specify that thecontent of a microsite can only be presented between 8 AM and 8 PM onweekdays and between 12 PM and 11 PM on weekends; that the content of amicrosite can only be presented when the user is located in her homestate of Virginia; that the content of a microsite can only be presentedwhen the user is moving at a speed of less than 20 KPH; or the like.

In some implementations, display component 3940 may present the contentof the microsite on the display of user device 3810 for a particularamount of time and, thereafter, remove the content of the microsite fromthe display. In some example implementations, the particular amount oftime may be configurable by the user of user device 3810. In someexample implementations, the particular amount of time may be preset byapplication component 3910, by an entity associated with ranking system3820, or by an entity associated with server 3830 hosting the content ofthe microsite.

In some implementations, display component 3940 may present the contentof the microsite within a particular region of the display of userdevice 3810. The particular region may include the entire display areaof the display or a subset of the entire display area of the display. Insome example implementations, the size and/or location of the particularregion may be configurable by the user of user device 3810. In someexample implementations, the size and/or location of the particularregion may be preset by application component 3910, by an entityassociated with ranking system 3820, or by an entity associated withserver 3830 hosting the content of the microsite.

A user may interact with the content of the microsite to dismiss thecontent—e.g., by swiping the content—or to obtain additional informationregarding the content—e.g., by selecting the content. The user'sinteraction with the microsite content may be recorded as user profiledata by user profile component 3920.

Although FIG. 39 shows example functional components of user device3810, in some implementations, user device 3810 may include additionalfunctional components, different functional components, or fewerfunctional components than those depicted in FIG. 39. Additionally, oralternatively, one or more functional components of user device 3810 mayperform one or more tasks described as being performed by one or moreother functional components of user device 3810.

FIG. 40 is a diagram of example functional components of ranking system3820. In some implementations, the functional components, shown in FIG.40, may be implemented by ranking system 3820. In some implementations,one or more of the functional components, shown in FIG. 40, may beimplemented by a system or device separate from ranking system 3820,such as a user device 3810 operating alone or in combination withranking system 3820. As shown in FIG. 40, ranking system 3820 mayinclude an input component 4010, an indexing component 4020, and aranking component 4030.

Input component 4010 may identify microsites for use by ranking system3820. In some implementations, input component 4010 may identifymicrosites through crawling. For example, input component 4010 mayinclude or interact with a crawler to locate microsites on a network,such as network 3840. The crawler may follow links to locate documentson the network. Input component 4010 may determine which documents aremicrosites by locating particular information on documents that aremicrosites. This particular information may include a piece of code thatidentifies the document as a microsite.

In some implementations, input component 4010 may identify micrositesvia manual input. For example, input component 4010 may provide a userinterface via which microsite designers may provide informationregarding microsites that the microsite designers have created. In someimplementations, a microsite designer, via the user interface, mayidentify a network address, such as a URL, associated with a microsite.Additionally, or alternatively, the microsite designer, via the userinterface, may upload the content of the microsite. The content of themicrosite may be hosted by ranking system 3820 or a device separate fromranking system 3820, such as a server 3830.

Input component 4010 may also provide a user interface that allowsmicrosite designers to specify other information in relation to amicrosite. For example, the user interface may allow a micrositedesigner to specify triggering criteria that dictate when the designer'smicrosite is to be presented—e.g., pushed—to a user device 3810, and aname for the microsite.

Indexing component 4020 may include one or more indexes that may bestored in one or more memory devices, which may be co-located orremotely located. In some implementations, indexing component 4020 maystore information regarding various microsites in an index. For aparticular microsite, for example, the index may store a descriptivename of the particular microsite, a network address for the particularmicrosite, triggering criteria for the particular microsite, and/or alist of sensors that are relevant for the particular microsite. Rankingcomponent 4030 may use the information in the index to identifymicrosites that are relevant for a particular user and/or in aparticular situation.

Ranking component 4030 may receive user profile data and sensor datafrom user device 3810. Ranking component 4030 may use the user profiledata and/or the sensor data to identify relevant microsites. In someimplementations, ranking component 4030 may identify microsites that arerelevant based on the sensor data and the triggering criteria, comparethe sensor data to the triggering criteria for the microsites, andgenerate scores for the microsites based on a result of the comparisons.For example, ranking component 4030 may perform a first analysis toidentify relevant microsites based on the sensor data and the triggeringcriteria; and perform a second analysis on the relevant microsites,based on a comparison of the sensor data and the triggering criteria, togenerate a score for each of the relevant microsites.

In some example implementations, ranking component 4030 may modify thescore, of a microsite, based on one or more factors. For example,ranking component 4030 may modify the score, of a microsite, based on apopularity score of the microsite. In some implementations, thepopularity score of a microsite may be generated based on user behaviordata associated with the microsite, such as how many users expresseddisinterest in the microsite by, for example, swiping away from themicrosite or providing a negative rating when the microsite waspresented to a user device 3810, and/or how many users expressedinterest in the microsite by, for example, providing a positive ratingwhen the microsite was presented to a user device 3810, requestingadditional information regarding the microsite, or purchasing a serviceassociated with the microsite. In some implementations, the popularityscore of a microsite may be generated using one or more factors insteadof, or in addition to, the user behavior data, such as a quantity oftimes that the microsite has been presented to user devices 3810, an ageof the microsite, a prior ranking or score of the microsite, or thelike.

Additionally, or alternatively, ranking component 4030 may modify thescore, of a microsite, based on a personalization score of themicrosite. In some implementations, the personalization score of amicrosite may be generated based on the user profile data, such as useractivity data, associated with a user of a particular user device 3810,with regard to the microsite. The user activity data may include, forexample, information relating to whether the user has expresseddisinterest in the microsite by, for example, swiping away from themicrosite or providing a negative rating when the microsite waspresented to the particular user device 3810, and/or whether the userexpressed interest in the microsite by, for example, providing apositive rating when the microsite was presented to the particular userdevice 3810, requesting additional information regarding the microsite,purchasing a service associated with the microsite, bookmarking themicrosite, and/or following a recommendation provided by themicrosite—e.g., a recommendation to visit a particular restaurant, see aparticular movie, ride a particular bus, or the like. In someimplementations, the personalization score of a microsite may begenerated using one or more factors instead of, or in addition to, theuser activity data, such as whether the user has recommended themicrosite to one of the user's social contacts.

Additionally, or alternatively, ranking component 4030 may modify thescore, of a microsite, based on a social score of the microsite. In someimplementations, the social score of a microsite may be generated basedon social contact activity data, associated with social contacts—e.g.,friends—of the user of a particular user device 3810, with regard to themicrosite. The user's social contacts may be identified based on theuser's communications, the user's address book, and/or the user'saccount on one or more social networks. Examples of social contactactivity data, associated with a microsite, include whether the user'ssocial contacts have expressed disinterest in the microsite by, forexample, swiping away from the microsite or providing a negative ratingwhen the microsite was presented to the social contacts' user devices3810, and/or whether the user's social contacts expressed interest inthe microsite by, for example, providing a positive rating when themicrosite was presented to the social contacts' user devices 3810,requesting additional information regarding the microsite, purchasing aservice associated with the microsite, bookmarking the microsite, and/orfollowing a recommendation provided by the microsite—e.g., arecommendation to visit a particular restaurant, see a particular movie,ride a particular bus, or the like. In some implementations, the socialscore of a microsite may be generated using one or more factors insteadof, or in addition to, the social contact activity data, such as whetherthe social contacts have recommended the microsite to others.

In some implementations, ranking component 4030 may generate a totalscore for a microsite based on a combination of the score and thepopularity score, the personalization score, and/or the social score. Insome implementations, ranking component 4030 may generate a total scorefor a microsite based on a combination of the score, the popularityscore, the personalization score, and the social score. In someimplementations, ranking component 4030 may generate a total score for amicrosite based on a weighted combination of the score, the popularityscore, the personalization score, and the social score. For example,ranking component 4030 may assign a weight value to the score, thepopularity score, the personalization score, and/or the social score.The weight values may differ—in other words, the amount that each of thescore, the popularity score, the personalization score, and the socialscore contributes to the total score may vary. Ranking component 4030may combine the weighted score, the weighted popularity score, theweighted personalization score, and/or the weighted social score togenerate the total score.

Ranking component 4030 may rank the relevant microsites, based on theirscores, to form a ranked list of microsites. Ranking component 4030 mayselect a set of microsites from the ranked list. For example, rankingcomponent 4030 may select the top scoring X microsites (X≥1). In someimplementations, ranking component 4030 may select only the top scoringmicrosite (X=1). In some implementations, ranking component 4030 mayselect the top scoring five (5) microsites (X=5).

In some implementations, the user profile data may indicate that one ormore of the relevant microsites, in the ranked list, have been purchasedby user device 3810. In these implementations, ranking component 4030may adjust the ranking of the one or more relevant microsites, in theranked list, by, for example, moving those purchased microsites to thetop of the ranked list. Thus, those relevant microsites, which have beenpurchased by user device 3810, may be ranked more highly than thoserelevant microsites that have not been purchased by user device 3810.

In some implementations, when ranking component 4030 determines that theuser profile data indicates that one or more of microsites, in set ofmicrosites that have been identified as relevant to received sensordata, have been purchased by user device 3810, ranking component 4030may generate scores for only the one or more purchased microsites. Inaddition, ranking component 4030 may form a list that includes onlythose microsites that have been purchased. In these situations, rankingcomponent 4030 may form a ranked list by sorting the microsites, in theformed list, based on their scores and/or other factors.

In any of the above situations, ranking component 4030 may provideinformation, regarding the ranked list of microsites, to user device3810. In some implementations, the information may include a networkaddress and/or a list of sensors for each microsite in the set ofmicrosites. In some implementations, the network addresses of themicrosites may be provided in a ranked list based on the scores of themicrosites. In some implementations, the network addresses of themicrosites may be provided along with the scores of the microsites.

Although FIG. 40 shows example functional components of ranking system3820, in some implementations, ranking system 3820 may includeadditional functional components, different functional components, orfewer functional components than those depicted in FIG. 40.Additionally, or alternatively, one or more functional components ofranking system 3820 may perform one or more tasks described as beingperformed by one or more other functional components of ranking system3820.

FIG. 41 is a flowchart of an example process 4100 relating to purchasinga microsite. In some implementations, process 4100 may be performed byuser device 3810. In some implementations, one or more blocks of process4100 may be performed by one or more devices instead of, or possibly inconjunction with, user device 3810.

Process 4100 may include accessing a microsite store (block 4110). Forexample, application component 3910, of user device 3810, may access amicrosite store, which provides information regarding microsites thatmay be purchased. In some implementations, a user may cause applicationcomponent 3910 to access the microsite store via, for example, a browseror in another manner.

Process 4100 may include purchasing a microsite (block 4120). Forexample, the user, of user device 3810, may review the micrositesassociated with the microsite store. The user may, for example, reviewdescriptions of the microsites, ratings of the microsites, prices of themicrosites, etc. Upon identifying a microsite of interest, the user maycause application component 3910 to provide monetary payment for themicrosite. In some implementations, application component 3910 mayprovide the monetary payment to ranking system 3820. In someimplementations, application component 3910 may provide the monetarypayment to another system or device.

Process 4100 may include providing triggering criteria for the microsite(block 4130). For example, application component 3910 may cause a listof triggering criteria, for the purchased microsite, to be provided tothe user. As indicated above, the triggering criteria dictate when thepurchased microsite will be provided to user device 3810 for display. Insome implementations, the list of triggering criteria may includetriggering criteria that have been provided by a designer of themicrosite. In some implementations, the user, of user device 3810, maychoose to accept the list of triggering criteria or modify one or moreof the triggering criteria in the list. For example, assume that thepurchased microsite is associated with the following triggeringcriteria: that user device 3810 is located in a particular geographicarea, that the time is not between 11 PM and 7 AM, and that user device3810 is currently detecting music being played. The user may modify thetriggering criteria by, for example, removing one or more of thetriggering criteria, adding one or more new triggering criteria, and/orediting one or more of the triggering criteria. With respect to theexample given above, assume that the user is regularly awake untilmidnight. Thus, the user may decide to modify the time-relatedtriggering criterion to change the time range from 11 PM to 7 AM to 12AM to 7 AM.

Process 4100 may include storing information relating to the purchasedmicrosite in a user profile (block 4140). For example, upon completionof the purchase, application component 3910 may store information, inuser profile component 3920, identifying the purchased microsite. Insome implementations, the information identifying the purchasedmicrosite may include an address—e.g., a URL or URI—of the purchasedmicrosite, along with a data and/or time of purchase. Additionally, inthose situations where the user has elected to modify the triggeringcriteria associated with the purchased microsite, application component3910 may store, in user profile component 3920, the modified triggeringcriteria.

While FIG. 41 shows process 4100 as including a particular quantity andarrangement of blocks, in some implementations, process 4100 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIG. 42 is a flowchart of an example process 4200 for providing contentof a microsite. While FIG. 42 shows process 4200 as including aparticular sequence of interactions among user device 3810, rankingsystem 3820, and a server 3830, in some implementations, some of theseinteractions may occur in another order or in parallel. Moreover, someof the blocks of process 4200 may be performed by a different device orgroup of devices, including or excluding user device 3810, rankingsystem 3820, and server 3830.

Process 4200 may include obtaining sensor data (block 4205). Forexample, application component 3910, of user device 3810, may obtainsensor data from sensors component 3930 associated with user device3810. Examples of sensor data were provided above with respect to FIG.39.

Process 4200 may include providing the sensor data and user profile data(block 4210). For example, application component 3910 may provide thesensor data to ranking system 3820. Application component 3910 may alsoprovide user profile data to ranking system 3820. Examples of userprofile data were provided above with respect to FIG. 39. As indicatedabove, the user profile data may include, in those instances where auser, of user device 3810, purchased a microsite, information relatingto the purchased microsite. For example, the information may includeinformation identifying the microsite, such as a network address,information identifying a date on which the microsite was purchased,information identifying a time at which the microsite was purchased,ranking and/or rating information for the microsite, etc. In addition,in those situations where the user modified the triggering criteria fora purchased microsite, the profile data may include informationidentifying the modified triggering criteria.

Application component 3910 may automatically—e.g., without requiring aninstruction from a user of user device 3810—provide the sensor data andthe user profile data to ranking system 3820. The user, of user device3810, may stop, at any time, the sending of sensor data and/or userprofile data to ranking system 3820.

Process 4200 may further include receiving the sensor data and the userprofile data (block 4215). For example, ranking component 4030, ofranking system 3820, may receive the sensor data and the user profiledata from user device 3810.

Process 4200 may include ranking microsites, identified using an index,based on the sensor data, the triggering criteria associated with themicrosites, and the user profile data (block 4220). For example, rankingcomponent 4030 may use the sensor data and/or the user profile data, toidentify relevant microsites. For example, ranking component 4030 maycompare the sensor data to the triggering criteria for a microsite,identified by the index or the user profile data, and generate a scorefor the microsite based on a result of the comparison. As describedabove, in some implementations, ranking component 4030 may modify thescore, for a microsite, based on one or more factors to generate a totalscore for the microsite. Ranking component 4030 may use the score, ortotal score, to form a ranked list of microsites. In someimplementations, ranking component 4030 may modify the ranked list ofmicrosites in those situations where a microsite, in the ranked list,was purchased by a user of user device 3810. In these situations,ranking component 4030 may modify the ranked list by moving informationidentifying the purchased microsite to the top of the ranked list.Further details regarding block 4220 are provided below with respect toFIGS. 43A and 43B.

Process 4200 may include providing information regarding the ranked listof microsites (block 4225). For example, ranking component 4030 mayprovide information regarding the ranked list of microsites to userdevice 3810. As explained above, in some implementations, theinformation may include, for each microsite in the ranked list ofmicrosites, a network address for the microsite and a list of sensorsrelevant to the microsite.

Process 4200 may include receiving the information regarding the rankedlist of microsites (block 4230). For example, application component3910, of user device 210, may receive the information regarding theranked list of microsites from ranking component 4030.

Process 4200 may include providing a request for a microsite in theranked list (block 4235). For example, based on receiving theinformation regarding the ranked list of microsites, display component3940, of user device 3810, may obtain sensor data associated with thelist of sensors that have been identified as relevant to the micrositesin the ranked list. For each relevant microsite, display component 3940may generate a request that includes the network address for therelevant microsite and the sensor data relevant to the relevantmicrosite. Display component 3940 may provide the request to one or moreservers 3830. Whether display component 3940 provides the requests tomore than one server 3830 depends on which server(s) 3830 is/are hostingthe relevant microsites. In other words, all of the relevant micrositesmay be hosted by a single server 3830, all of the relevant micrositesmay be hosted by separate, different servers 3830, or something inbetween these two extremes.

Process 4200 may include receiving a request for a microsite (block4240). For example, server 3830 may receive a request, for a microsite,from user device 3810 and obtain content of the relevant microsite. Insome implementations, the content of a relevant microsite may be dynamicin the sense that the content of the relevant microsite may be based onthe sensor data received from user device 3810.

Process 4200 may include providing the microsite (block 4245). Forexample, server 3830 may provide the content of the relevant micrositeto user device 3810.

Process 4200 may include receiving the content of the microsite (block4250). For example, display component 3940, of user device 3810, mayreceive the content of the microsite from server 3830.

Process 4200 may include rendering the content of the microsite (block4255). For example, display component 3940 may present the content ofthe microsite on a display associated with user device 3810. Whencontent is received for multiple microsites, display component 3940 maypush the content, for the relevant microsites, as a sliding display ofcontent. In some implementations, content for one of the relevantmicrosites may be presented on the display at a time. A user, of userdevice 3810, may interact with the content, using a finger or the like,to express the user's interest or disinterest in the content or to seethe content for another one of the relevant microsites.

While FIG. 42 shows process 4200 as including a particular quantity andarrangement of blocks, in some implementations, process 4200 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIGS. 43A and 43B is a flowchart of an example process 4300 that maycorrespond to block 4220 of FIG. 42. In some implementations, process4300 may be performed by ranking system 3820. In some implementations,one or more blocks of process 4300 may be performed by one or moredevices instead of, or possibly in conjunction with, ranking system3820.

Process 4300 may include identifying a group of relevant micrositesbased on the sensor data and the triggering criteria (block 4305, FIG.43A). For example, ranking component 4030, of ranking system 3820, mayidentify microsites that are relevant to the sensor data by comparingthe sensor data to the triggering criteria for the microsites. Asindicated above, the triggering criteria, for a particular microsite,may be included in the index and/or identified in the user profiledata—e.g., in those situations where the user, of user device 3810, hasmodified the triggering criteria. In some implementations, rankingcomponent 4030 may identify microsites that are relevant based oninformation in the user profile data and by comparing the sensor data tothe triggering criteria for the microsites. Other ways of identifyingrelevant microsites may alternatively be used.

Process 4300 may include generating a score for each microsite in thegroup of microsites (block 4310). For example, ranking component 4030may generate scores for the microsites, in the group of microsites,based on one or more factors. For example, ranking component 4030 maygenerate a score, for a microsite, based on comparing the sensor data tothe triggering criteria associated with the microsite.

In some implementations, ranking component 4030 may generate the scoresfor the microsites based on the quantity of triggering criteria in thetriggering criteria. For example, if the triggering criteria for a firstrelevant microsite include 5 different triggering criteria and if thetriggering criteria for a second relevant microsite include 2 differenttriggering criteria, ranking component 4030 may generate a higher scorefor the first relevant microsite than the second relevant microsite.

In some implementations, ranking component 4030 may generate scores forthe microsites based on a degree to which the sensor data matches thetriggering criteria. For example, assume that the sensor data indicatesthat the current time is 8:55 PM. Also, assume that a first set oftriggering criteria, for a first relevant microsite, includes a timerange of 8 PM to 1 AM, and a second set of triggering criteria, for asecond relevant micro site, includes a time range of 8 PM to 9 PM. Sincethe current time, as indicated by the sensor data, is closer to thebeginning of the time range for the first set of triggering criteria andcloser to the end of the time range for the second set of triggeringcriteria, ranking component 4030 may give a higher score to the firstrelevant microsite than the second relevant microsite.

In some implementations, ranking component 4030 may generate an initialscore for each microsite, in the group of microsites, based on thesensor data and/or the user profile data. Ranking component 4030 maymodify the initial score, of a microsite, based on one or more factorsto obtain the score for the microsite. The one or more factors mayinclude, for example, a popularity score of the microsite, apersonalization score of the microsite, a social score of the microsite,and/or another factor. The popularity score, the personalization score,and the social score were discussed above with respect to FIG. 40. Otherways of obtaining a score for a microsite may alternatively be used.

Process 4300 may include determining whether the group of micrositesincludes a single microsite that has been purchased (block 4315). Forexample, ranking component 4030 may parse the user profile data,provided by user device 3810, to identify microsites that have beenpurchased. Ranking component 4030 may compare the identified micrositesto the microsites in the group of relevant microsites to determinewhether the group of microsites includes a single purchased microsite.

When the group of microsites includes single purchased microsite (block4315—YES), process 4300 may include creating a list of microsites thatare sorted based on the generated scores (block 4320). For example,ranking component 4030 may create a list that includes informationidentifying the microsites. Ranking component 4030 may sort the list indescending order, such that information identifying the microsite withthe highest generated score appears at the top of the list andinformation identifying the microsite with the lowest generated scoreappears at the bottom of the list.

Process 4300 may include moving the single purchased microsite to thetop of the sorted list to create a ranked list of microsites (block4325). For example, ranking component 4030 may create a ranked list ofmicrosites by moving the information for the single purchased micrositeto the top of the sorted list. In this way, ranking component 4030ensures that the single purchased microsite is rendered, by user device3810, before non-purchased microsites in the ranked list.

When the group of microsites does not include a single purchasedmicrosite (block 4315—NO), process 4300 may include determining whetherthe group of microsites includes more than one purchased microsite(block 4330). For example, ranking component 4030 may parse the userprofile data, provided by user device 3810, to identify microsites thathave been purchased. Ranking component 4030 may compare the identifiedmicrosites to the microsites in the group of relevant microsites todetermine whether the group of microsites includes multiple purchasedmicrosites.

When the group of microsites does not include more than one purchasedmicrosite (block 4330—NO), process 4300 may include creating a rankedlist of microsites by sorting the microsites, in the group ofmicrosites, based on the generated scores (block 4335). For example,ranking component 4030 may create a list that includes informationidentifying the microsites. Ranking component 4030 may generate a rankedlist of microsites by sorting the list in descending order, such thatinformation identifying the microsite with the highest generated scoreappears at the top of the list and information identifying the micrositewith the lowest generated score appears at the bottom of the list. Inthis way, ranking component 4030 ensures that the microsite, with thehighest generated score, is rendered, by user device 3810, before anyother microsite in the ranked list.

When the group of microsites includes more than one purchased microsite(block 4330—YES), process 4300 may include creating a list of micrositesthat are sorted based on the generated scores (block 4340, FIG. 43B).For example, ranking component 4030 may create a list that includesinformation identifying the microsites. Ranking component 4030 may sortthe list in descending order, such that information identifying themicrosite with the highest generated score appears at the top of thelist and information identifying the microsite with the lowest generatedscore appears at the bottom of the list.

Process 4300 may include determining whether the purchased micrositeshave been ranked or rated by the user (block 4345). For example, rankingcomponent 4030 may parse the user profile data, provided by user device3810, to determine whether the user has ranked and/or rated themicrosites that have been purchased. For example, the user profile datamay include information giving a ranking value to the purchasedmicrosites, where the ranking values are to be used if more than one ofthe purchased microsites are identified based on a given set of sensordata. As one example, assume that the user has purchased, via userdevice 3810, three microsites, named MICROSITE A, MICROSITE B, andMICROSITE C. In addition, assume that the user has specified, in theuser profile data, that if more than one of these purchased micrositesare identified based on sensor data, then the purchased microsites areto be ranked in the following order: MICROSITE C, MICROSITE B, andMICROSITE A. Thus, the user profile data, provided by user device 3810,may include this ranking information.

Similarly, the user profile data may include rating information thatindicates rating values for the purchased microsites. The rating valuesmay provide an indication of how much the user likes or dislikes thepurchased microsites. As one example, assume that the user haspurchased, via user device 3810, three microsites, named MICROSITE A,MICROSITE B, and MICROSITE C. In addition, assume that the user hasgiven MICROSITE A a rating of 4, MICROSITE B a rating of 1, andMICROSITE C a rating of 3. The user profile data, provided by userdevice 3810, may include this rating information.

When the purchased microsites have been ranked or rated by the user(block 4345—YES), process 4300 may include moving the purchasedmicrosites to the top of the sorted list, in an order based on therankings/ratings, to create a ranked list of microsites (block 4350).For example, ranking component 4030 may create a ranked list ofmicrosites by moving the information for the purchased microsites to thetop of the sorted list. Ranking component 4030 may sort the purchasedmicrosites, at the top of the sorted list, based on the rankings/ratingsin the user profile data. For example, if the user profile data includesranking information, ranking component 4030 may rank the purchasedmicrosites in the order specified by the ranking information. Thus, inthe example given above, if the sorted list of microsites includesMICROSITE A and MICROSITE B, ranking component 4030 may move informationidentifying MICROSITE B to the top of the list, followed by informationidentifying MICROSITE A.

If the user profile data includes rating information, ranking component4030 may rank the purchased microsites in the order specified by therating information. Thus, in the example given above, if the sorted listof microsites includes MICROSITE A, MICROSITE B, and MICROSITE C,ranking component 4030 may move information identifying MICROSITE A tothe top of the list, followed by information identifying MICROSITE C,and followed by information identifying MICROSITE B.

If the user profile data includes ranking information and ratinginformation, ranking component 4030 may rank the purchased microsites inan order based on the ranking information and the rating information. Insome implementations, ranking component 4030 may consider the rankinginformation and may ignore the rating information in determining how torank the purchased microsites in the sorted list. In someimplementations, ranking component 4030 may consider the ratinginformation and may ignore the ranking information in determining how torank the purchased microsites in the sorted list. In someimplementations, ranking component 4030 may assign weights to the ratinginformation, where those weights may affect the ranking information forthe purchased microsites. Other manners of using the ranking informationand the rating information to determine an order of the purchasedmicrosites, in the sorted list, may alternatively be used.

In this way, ranking component 4030 may ensure that the purchasedmicrosites are rendered, by user device 3810, before non-purchasedmicrosites in the ranked list.

When the microsites have not been ranked or rated by the user (block4345—NO), process 4300 may include determining whether the generatedscore of one purchased microsite is larger than the generated score foranother purchased microsite (block 4355). For example, ranking component4030 may compare the generated scores of the purchased microsites todetermine whether the score of one purchased microsite is larger thanthe score of another purchased microsite.

When the generated score of one purchased micro site is larger than thegenerated score for another purchased microsite (block 4355—YES),process 4300 may include moving the purchased microsites to the top ofthe sorted list, in an order based on the generated scores, to create aranked list of microsites (block 4360). For example, ranking component4030 may create a ranked list of microsites by moving the informationfor the purchased microsites to the top of the sorted list. Rankingcomponent 4030 may sort the purchased microsites, at the top of thesorted list, based on the generated scores. For example, assumingranking component 4030 generates a score of 0.9 for MICROSITE A and ascore of 0.95 for MICROSITE B, ranking component 4030 may moveinformation identifying MICROSITE B to the top of the list, followed byinformation identifying MICROSITE A.

In this way, ranking component 4030 may ensure that the purchasedmicrosites are rendered, by user device 3810, before non-purchasedmicrosites in the ranked list.

When the generated score of one purchased micro site is not larger thanthe generated score for another purchased microsite (block 4355—NO),process 4300 may include moving the purchased microsites to the top ofthe sorted list, in an order based on the dates/times that themicrosites were purchased, to create a ranked list of microsites (block4365). For example, ranking component 4030 may create a ranked list ofmicrosites by moving the information for the purchased microsites to thetop of the sorted list. Ranking component 4030 may sort the purchasedmicrosites, at the top of the sorted list, based on the dates/times thatthe microsites were purchased. In some implementations, rankingcomponent 4030 may sort the purchased microsites in a descendingdate/time order. For example, assume that MICROSITE A was purchased onJul. 12, 2011 and that MICROSITE B was purchased on Nov. 29, 2010. Inthis situation, ranking component 4030 may move information identifyingMICROSITE A to the top of the list, followed by information identifyingMICROSITE B. Other ways for sorting the purchased microsites based onthe dates/times of purchase may alternatively be used.

In this way, ranking component 4030 may ensure that the purchasedmicrosites are rendered, by user device 3810, before non-purchasedmicrosites in the ranked list.

While FIG. 43 shows process 4300 as including a particular quantity andarrangement of blocks, in some implementations, process 4300 may includefewer blocks, additional blocks, or a different arrangement of blocks.Additionally, or alternatively, some of the blocks may be performed inparallel.

FIGS. 44A-44D are an example 4400 of the process described above withrespect to FIGS. 42-43B. With reference to FIG. 44A, assume a user,named Mary, has purchased a workout microsite that provides a user, whohas gone out for a run, with information regarding the distance that theuser has run, the speed at which the user is running, and the number ofcalories that the user has burned. As a result of the purchase, a userprofile, associated with Mary or a user device (shown as a watch in FIG.44A) that is associated with Mary, may store information identifying theworkout microsite.

Further, assume, as shown in FIG. 44A, that Mary's watch periodicallysends, as depicted by reference number 4410, sensor data and userprofile data to ranking system 3820. In addition, assume that the userprofile data includes, among other things, information identifying theworkout microsite.

With reference to FIG. 44B, ranking component 4030, of ranking system3820, may receive sensor data and user profile data 4410. Rankingcomponent 4030 may identify a group 4420 of microsites that are relevantto the sensor data and/or the user profile data and generate a score4430 for each microsite in group 4420. Ranking component 4030 may sortthe microsites, in group 4420, based on scores 4430 to form a sortedlist 4440 of microsites. As shown in FIG. 44B, sorted list 4440 includesa bus stops microsite as the top ranking microsite, followed by a coffeemicrosite, the workout microsite, a restaurant microsite, and a banksmicrosite. Since the workout microsite was purchased by Mary, rankingcomponent 4030 may modify sorted list 4440, by moving the workoutmicrosite to the top of the list, to create a ranked list 4450. A shown,ranked list 4450 includes the workout microsite as the top rankingmicrosite, followed by the bus stops microsite, the coffee microsite,the restaurant microsite, and the banks microsite.

With reference to FIG. 44C, ranking system 3820 may provide ranked list4450 to Mary's watch. In addition to ranked list 4450, ranking system3820 may provide other information, as discussed above, such as a listof sensors for each microsite identified in ranked list 4450.

With reference to FIG. 44D, Mary's watch may receive ranked list 4450and send a request for one or more of the microsites in ranked list4450. Since the workout microsite is the highest ranking microsite inranked list 4450, Mary's watch may cause the workout microsite to berendered for display prior to the other microsites in ranked list 4450.Thus, since Mary paid for the workout microsite, the workout micrositemay be given priority over other microsites, including higher scoringmicrosites.

A system and method, described herein, may cause a purchased micrositeto be presented (e.g., pushed) to a user device before other microsites,including microsites that may be scored higher than the purchasedmicrosite. The purchased microsite may provide information that may beuseful to the user.

Example 5

FIG. 45 is a schematic diagram of an example system 4500 including asignal based recommender system 4502. In some implementations, thesignal based recommender system 4502 includes data processing apparatuse.g., handheld devices, rack-mounted servers, or other computingdevices. The data processing apparatus within the signal basedrecommender system 4502 can be in the same physical location (e.g., datacenter) or can be in different physical locations. The data processingapparatus and user devices communicatively coupled to the signal basedrecommender system 4502 can have different capabilities and computerarchitectures. In some implementations, the user device 4508 is apersonal computer, a laptop computer, a watch, a tablet computer, or amobile device.

The signal based recommender system 4502 can use crowd-sourced contentsegments to identify user intentions. The signal based recommendersystem 4502 can obtain crowd-sourced (e.g., sent by many users) contentand other information (e.g., location) from public sites. Public sitesare sites that can be accessed at least in part without requiring alogin. For example, public sites contain publicly available content. Oneor more user devices (e.g., a user device 4508) can communicate with thesignal based recommender system 4502 using a network 4510. The signalbased recommender system 4502 can provide one or more search resultsthat can predict what a user might intend to search given a location andpreviously obtained content segments around the user's location.

In some implementations, a classifier 4504 resides within the signalbased recommender system 4502. In some other implementations, theclassifier 4504 resides on a data processing apparatus separate from thesignal based recommender system 4502. The classifier 4504 can classifycontent segments into categories. The use of categories can aid a searchsystem in increasing relevancy of its search results. In someimplementations, a search system 4505 resides within the signal basedrecommender system 4502. In some other implementations, the searchsystem 4505 resides on a data processing apparatus separate from thesignal based recommender system 4502. The search system 4505 can performsearches on relevant content segments to obtain a search result.

The signal based recommender system 4502 can also communicate with adatabase 4506. The database 4506 is an electronic file system, adistributed file system, or other network-accessible persistent storagethat can store information on computer-readable storage media. In someimplementations, the database 4506 is a database of intentions. Thedatabase of intentions includes data representing a general intention ofusers who perform mobile searches or access social media content, whichcan be data obtained from social networks. For example, if a user enters“gourmet restaurants” as a mobile search query, the system determinesthat the user intends to find information about gourmet restaurants.

FIG. 46 is a flowchart of an example method 4600 of the signal basedrecommender system to identify user intentions. For convenience, themethod 4600 will be described with respect to a system having one ormore computing devices that performs the method 4600.

The system obtains content segments from various sources 4602. Thesystem can retrieve numerous content segments from multiple sources. Insome implementations, content segments are “crowd-sourced” such that thecontent segments correspond to information that is entered by manyusers. For example, potential sources of crowd-sourced content segmentsinclude social network feeds and posts to social sites or blogs. Sourcesof content segments can also include mobile search queries entered by agroup of users.

After receiving content segments, the system can aggregate the contentsegments and process them. The initial processing can include one ormore of spam removal, clustering, high frequency, and local relevance.In some implementations, if a content segment is not filtered out as aresult of the processing, the content segment is entered into a databaseof intentions.

The system can filter the content segments according to a classificationalgorithm trained to filter spam information 4604. Spam information canbe unwanted or unsolicited information that is marketing a product orservice (e.g., pornography). Spam information can also include highfrequency terms that lead to high trafficked sites, e.g., a searchengine destination page or a social network page. The system can filterout spam information by detecting spam-like keywords. For example,search queries associated with pornography can be filtered out. Theclassification algorithm can be implemented, for example, using aclassifier (e.g., classifier 4504 within the signal based recommendersystem 4502 or a separate classifier from the signal based recommendersystem 4502).

The system clusters the content segments 4606. In some implementations,the system clusters the content segments to aggregate content segmentswith small typographical differences. For example, if text of onecontent segment is “gourmet restaurant” while text of another contentsegment has ‘restaurant’ misspelled, e.g., “gourmet restarants,” theaggregation of the two content segments can result in one contentsegment of “gourmet restaurant.”

The system can also cluster content segments to remove duplicates. Forexample, if text of two unique content segments both contain “gourmetrestaurant,” the aggregation of the two content segments can result inone content segment of “gourmet restaurant.” This filtering allows thesystem to remove repeated entries of content segments. When the systemaggregates content segments, the system keeps track of each contentsegment's aggregation frequency and considers the aggregation frequencyas a factor in determining a popularity metric as will be describedbelow. In some implementations, the server uses hierarchicalagglomerative clustering (HAC) to cluster the content segments.

The clustered content segments can be filtered according to a frequencythreshold 4608. The system implements the frequency threshold to removerarely occurring content segments. If a content segment does not appearenough to meet the frequency threshold, the system determines that thecontent segment is not relevant enough to present to users. In someimplementations, the frequency threshold is a specified value indicatinga frequency of occurrence of the content segment (e.g., the contentsegment must appear at least 50 times). In some other implementations,the frequency threshold is dynamically adjusted by the system based onone or more criteria (e.g., the number of received total contentsegments, or the number of received content segments over a specifiedtime).

The content segments are filtered by a local relevance score 4610. Alocal relevance score can be based on one or more signals of a contentsegment. In some implementations, these signals include location, time,aggregation frequency of the content segment, current events, or otherinformation. For example, the system may give a higher local relevancescore to a content segment about a highly-searched event near a locationat a certain time. Also, mobile searches can be given a higher localrelevance score because mobile searches can include metadata about alocation and a timestamp at which the search occurred. In someimplementations, if the local relevance score is low, the systemdiscards the content segment.

After some content segments are filtered out, the system classifies theremaining content segments into categories 4612. The categories can belocally relevant. For example, categories include places, movies,shopping items, health, or weather. The system uses a classifier togroup content segments into categories.

The system assigns each content segment a popularity metric 4614. Thepopularity metric indicates a level of a content segment's appearancefrequency. In some implementations, the popularity metric is based onthe number of search queries that include the content segment. In someimplementations, the popularity metric is based on one or moreparameters that indicate a number of “reposts” on social media channels(e.g., social feeds, social sites). A repost can be a content segmentthat has previously been posted on a social media website. For example,if a content segment is a mobile search query about a popular event andthe mobile search query has metadata including a timestamp, the contentsegment may be given a higher score if the current time at the locationis close to the timestamp embedded in the mobile query search. Inanother example, if a content segment is about a movie, the contentsegment may be given a higher score if the movie is a new movie that hasjust been released. If a content segment is about a sale at a departmentstore and the content segment includes an end date of the sale, thecontent segment may be given a higher score if the sale is endingshortly and reassigned a lower score after the sale ends. In somealternative implementations, instead of assigning a popularity metric,the system assigns a social graph distance that measures how relevantthe content segment is to a user.

In some implementations, if the content segment is a mobile searchquery, the system also filters out the mobile search query's “longtail,” meaning the system removes terms from the query if the query isover a specified length. For example, if text of the query is “gourmetrestaurants in san jose having a bar,” the system can remove the “longtail” and convert the content segment into “gourmet restaurants.”

After assigning each content segment a popularity metric, the systemstores the content segments 4616. For example, the system can input eachcontent segment along with one or more associated parameters into thedatabase of intentions. The one or more associated parameters can begenerated by the system, e.g., the popularity metric can be generated asdescribed above. Signals associated with the content segment can also bestored as associated parameters. For example, if the content segment isa mobile search query, signals associated with the content segment caninclude items of mobile search query metadata. The mobile search querymetadata can be obtained from search query logs. Alternatively, thesystem can obtain mobile search query metadata, along with othersignals, from data that is sent from one or more mobile devices. Forother kinds of content segments, signals associated with the contentsegment can include items of metadata otherwise associated with thecontent segment.

A row in a table of the database of intentions about a mobile searchquery includes a unique identification number, a date, an hour, alatitude and longitude geolocation, text of the content segment, acategory, a query count indicating a number of times the content segmenthas been queried, and a popularity metric. In some implementations, iftwo content segments are determined to be duplicates, the contentsegment having the higher popularity metric is stored. An example rowwithin a database of intentions is shown below:

Content Query Popularity ID Date Hour Latitude Longitude SegmentCategory Count metric Id = 3 2011 Jul. 19 20 34.0522 −118.2437 GourmetPlace 1000000 1.0 restaurant

An example row for a content segment about a social media post is shownbelow:

Content Repost Popularity ID Date Hour Latitude Longitude SegmentCategory Count metric Id = 4 2011 Jul. 18 11 26.0522 −95.2437 ballparkPlace 500 1.0

In some implementations, a row in the table of intentions is expanded toinclude a variety of signals based on sensors of a mobile device of auser. For example, other signals can include the acceleration of themobile device, or whether the mobile device is geographically near afriend of the user.

FIG. 47 is a flowchart of an example method 4700 of providing a searchresult to a user. For convenience, the method 4700 will be describedwith respect to a system having one or more computing devices thatperforms the method 4700.

The system receives a query 4702. The query can be received from a userdevice, for example, a computer, a laptop, a tablet, a watch, or amobile phone. The user device can submit the query, for example, toobtain a relevant entry from the database of intentions. In someimplementations, the user provides an input to the user device, which inturn causes the user device to send the query to the server. In somealternative implementations, the user does not provide any input to theuser device, but the user device periodically sends requests to thesystem. For example, the user device can request a response from theserver according to a fixed schedule or a location of the user device.The user device can also request a response from the server based oncontent segment activity around the user device's location (e.g., manycontent segments are added to the database of intentions near a locationat a specific time). The submission of the query can also be triggeredby different events, such as a wake-up from a user device's sleep mode.The query can contain information specific to the user device. Forexample, the query can contain location, time, user data, or priorsearch query data of the user device.

The system identifies a location of interest 4704 from a database ofintentions (e.g., a database of intentions described above with respectto FIG. 46) that is near the user device's location. In someimplementations, the location of interest is a city. In someimplementations, the location of interest includes all locations withina specified radius around the user device's location. The radius can befixed or dynamically adjusted by the system.

The system determines a relevant entry 4706 by identifying entries fromthe database of intentions that match the location of interest andselecting one entry that is near the identified location of interestbased on one or more factors discussed below. If the location ofinterest is a city, the system can determine a relevant entry thatrelates to the city, similarly for a neighborhood within a city. In someimplementations, the system considers a popularity metric for eachcontent segment. If the content segment is a mobile search query, thesystem considers the number of times the mobile search query has beenqueried. If the content segment is a social media post, the system canconsider the number of times the social media post is reposted. Thesystem can also consider one or more parameters that indicate a user'spreferences. For example, if a user has specified that the user wants asearch result related to restaurants, the system can determine arelevant entry from restaurants in the database of intentions.

The system also considers the location, date, and/or time associatedwith the user device when processing the query. For example, if a userdevice sends a query at 12 AM on a Friday and the user device is locatedoutside a bar, the system can consider the time, date, location, userpreferences, and popularity metric. If many users are searching for“taxi cabs” at the time, date, and location (e.g., using mobile searchqueries), a content segment about taxi cabs may have a high popularitymetric. If the content segment has the highest popularity metriccompared to other content segments, the system can select the contentsegment about “taxi cabs” as the most relevant entry.

In some implementations, the system filters out content segments thatinclude generic information less likely to be searched by a user. Forexample, if the content segment is about a city or country, the systemcan serve the next relevant result because the user presumably is notseeking information regarding the city or country in which he or she islocated.

After selecting the relevant entry, the system performs a local search(e.g., a search that has a restriction based on location) that includesthe entry's content segment 4708. In some implementations, the systemqueries a service for further details about the content segment. Forexample, if the content segment is in the place category, the systemqueries a places Application Program Interface (API) for moreinformation regarding the place. Information from the places API caninclude the content segment's address, location, reviews, telephonenumber, operating hours, or other local information. The server may alsosearch using other local API's.

The system can also perform a local search on the relevant entry byusing a search mechanism related to the category from the contentsegment's row in the database of intentions. For example, if the userwere to have submitted a query when the user is near a latitude andlongitude of (34.0522, −118.2437) at hour 20 on a day similar to 07/19(see table above), the system can determine “gourmet restaurant” as therelevant entry and run a “places” search for “gourmet restaurant”centered near the user device's coordinates using a search system withinthe signal based recommender system, or by submitting a search to asearch system.

After performing the local search, the system obtains one or moreresponsive search results. The system selects a search result from thesearch results. In some implementations, the system selects a specificsearch result by choosing the top-ranked search result.

In some alternative implementations, the system sends the relevant entryto a search engine. The search engine can show the relevant entry as asearch suggestion, e.g., the suggestion can be shown near or in a searchfield. The system provides information about the selected search resultto the user device 4710. In some implementations, the system obtains theinformation from local API's. For example, if the system searches for“gourmet restaurant,” the system can obtain multiple responsive localsearch results from an API including information about local businesses.If the selected search result is of a gourmet restaurant called “CountryGourmet Restaurants,” the system can obtain the name, address, phonenumber, and average reviews of Country Gourmet Restaurant (e.g., fromthe API) and send the information to the user device.

FIG. 48 is a diagram of an example user device 4800 that showsinformation about a provided search result. After sending a query, theuser device receives information about a relevant search result, e.g.,as described above with respect to FIG. 47. In some implementations, therelevant result is a restaurant. The user device can display the name ofthe restaurant 4802, the address and phone number 4804, and the averagereviews for the restaurant 4806. The user device 4800 can also display amap 4808 of where the restaurant is located. In some implementations,the relevant result is displayed on a lock screen of the user device4800 or as a screensaver for the user device 4800. In some otherimplementations, contact information for the relevant result isdisplayed as a suggestion in a phone interface of the user device 4800.In some alternative implementations, when starting a mapping applicationof the user device 4800, the mapping application displays drivingdirections corresponding to the relevant result.

Generic Computing Device and Mobile Computing Device

FIG. 49 is a diagram of an example of a generic computing device 4900and a generic mobile computing device 4950, which may be used with thetechniques described here. Generic computing device 4900 or genericmobile computing device 4950 may correspond to, for example, a userdevice 3810, ranking system 3820, and/or server 3830. Each of userdevice 3810, ranking system 3820, and/or server 3830 may include one ormore computing devices 4900, one or more mobile computing devices 4950,and/or one or more components of computing device 4900 or mobilecomputing device 4950.

Computing device 4900 is intended to represent various forms of digitalcomputers, such as laptops, desktops, workstations, personal digitalassistants, servers, blade servers, mainframes, and other appropriatecomputers. Mobile computing device 4950 is intended to represent variousforms of mobile devices, such as personal digital assistants, cellulartelephones, smart phones, and other similar computing devices. Thecomponents shown in FIG. 49, their connections and relationships, andtheir functions, are meant to be examples only, and are not meant tolimit implementations described herein.

Computing device 4900 may include a processor 4902, memory 4904, astorage device 4906, a high-speed interface 4908 connecting to memory4904 and high-speed expansion ports 4910, and a low speed interface 4912connecting to low speed bus 4914 and storage device 4906. Each of thecomponents 4902, 4904, 4906, 4908, 4910, and 4912, are interconnectedusing various busses, and may be mounted on a common motherboard or inother manners as appropriate. Processor 4902 can process instructionsfor execution within the computing device 4900, including instructionsstored in the memory 4904 or on the storage device 4906 to displaygraphical information for a graphical user interface (GUI) on anexternal input/output device, such as display 4916 coupled to high speedinterface 4908. In other implementations, multiple processors and/ormultiple buses may be used, as appropriate, along with multiple memoriesand types of memory. Also, multiple computing devices 4900 may beconnected, with each device providing portions of the necessaryoperations, as a server bank, a group of blade servers, or amulti-processor system, etc.

Memory 4904 stores information within the computing device 4900. In someimplementations, memory 4904 includes a volatile memory unit or units.In some implementations, memory 4904 includes a non-volatile memory unitor units. The memory 4904 may also be another form of computer-readablemedium, such as a magnetic or optical disk. A computer-readable mediummay refer to a non-transitory memory device. A memory device may referto storage space within a single storage device or spread acrossmultiple storage devices.

The storage device 4906 is capable of providing mass storage for thecomputing device 4900. In some implementations, storage device 4906 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described herein. The information carrier is a computer ormachine-readable medium, such as memory 4904, storage device 4906, ormemory on processor 4902.

High speed controller 4908 manages bandwidth-intensive operations forthe computing device 4900, while low speed controller 4912 manages lowerbandwidth-intensive operations. Such allocation of functions isexemplary only. In some implementations, high-speed controller 4908 iscoupled to memory 4904, display 4916 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 4910, which mayaccept various expansion cards (not shown). In these implementations,low-speed controller 4912 is coupled to storage device 4906 andlow-speed expansion port 4914. The low-speed expansion port, which mayinclude various communication ports (e.g., USB, Bluetooth, Ethernet,wireless Ethernet), may be coupled to one or more input/output devices,such as a keyboard, a pointing device, a scanner, or a networking devicesuch as a switch or router, e.g., through a network adapter.

Computing device 4900 may be implemented in a number of different forms,as shown in the figure. For example, it may be implemented as a standardserver 4920, or multiple times in a group of such servers. It may alsobe implemented as part of a rack server system 4924. In addition, it maybe implemented in a personal computer such as a laptop computer 4922.Alternatively, components from computing device 4900 may be combinedwith other components in a mobile device (not shown), such as mobilecomputing device 4950. Each of such devices may contain one or more ofcomputing devices 4900, 4950, and an entire system may be made up ofmultiple computing devices 4900, 4950 communicating with each other.

Mobile computing device 4950 may include a processor 4952, memory 4964,an input/output (“I/O”) device, such as a display 4954, a communicationinterface 4966, and a transceiver 4968, among other components. Mobilecomputing device 4950 may also be provided with a storage device, suchas a micro-drive or other device, to provide additional storage. Each ofthe components 4950, 4952, 4964, 4954, 4966, and 4968 are interconnectedusing various buses, and several of the components may be mounted on acommon motherboard or in other manners as appropriate.

Processor 4952 can execute instructions within mobile computing device4950, including instructions stored in memory 4964. Processor 4952 maybe implemented as a chipset of chips that include separate and multipleanalog and digital processors. Processor 4952 may provide, for example,for coordination of the other components of mobile computing device4950, such as control of user interfaces, applications run by mobilecomputing device 4950, and wireless communication by mobile computingdevice 4950.

Processor 4952 may communicate with a user through control interface4958 and display interface 4956 coupled to a display 4954. Display 4954may be, for example, a TFT LCD (Thin-Film-Transistor Liquid CrystalDisplay) or an OLED (Organic Light Emitting Diode) display, or otherappropriate display technology. Display interface 4956 may compriseappropriate circuitry for driving display 4954 to present graphical andother information to a user. Control interface 4958 may receive commandsfrom a user and convert them for submission to the processor 4952. Inaddition, an external interface 4962 may be provide in communicationwith processor 4952, so as to enable near area communication of mobilecomputing device 4950 with other devices. External interface 4962 mayprovide, for example, for wired communication in some implementations,or for wireless communication in other implementations, and multipleinterfaces may also be used.

Memory 4964 stores information within mobile computing device 4950.Memory 4964 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 4974 may also be provided andconnected to mobile computing device 4950 through expansion interface4972, which may include, for example, a Single In Line Memory Module(SIMM) card interface. Such expansion memory 4974 may provide extrastorage space for device 4950, or may also store applications or otherinformation for mobile computing device 4950. Specifically, expansionmemory 4974 may include instructions to carry out or supplement theprocesses described above, and may include secure information also.Thus, for example, expansion memory 4974 may be provide as a securitymodule for mobile computing device 4950, and may be programmed withinstructions that permit secure use of device 4950. In addition, secureapplications may be provided via the SIMM cards, along with additionalinformation, such as placing identifying information on the SIMM card ina non-hackable manner.

Expansion memory 4974 may include, for example, flash memory and/orNVRAM memory. In some implementations, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 4964, expansionmemory 4974, or memory on processor 4952, that may be received, forexample, over transceiver 4968 or external interface 4962.

Mobile computing device 4950 may communicate wirelessly throughcommunication interface 4966, which may include digital signalprocessing circuitry where necessary. Communication interface 4966 mayprovide for communications under various modes or protocols, such as GSMvoice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA,CDMA4900, or GPRS, among others. Such communication may occur, forexample, through radio-frequency transceiver 4968. In addition,short-range communication may occur, such as using a Bluetooth, Wi-Fi,or other such transceiver (not shown). In addition, Global PositioningSystem (GPS) receiver module 4970 may provide additional navigation- andlocation-related wireless data to mobile computing device 4950, whichmay be used as appropriate by applications running on mobile computingdevice 4950.

Mobile computing device 4950 may also communicate audibly using audiocodec 4960, which may receive spoken information from a user and convertit to usable digital information. Audio codec 4960 may likewise generateaudible sound for a user, such as through a speaker, e.g., in a handsetof mobile computing device 4950. Such sound may include sound from voicetelephone calls, may include recorded sound (e.g., voice messages, musicfiles, etc.) and may also include sound generated by applicationsoperating on mobile computing device 4950.

Mobile computing device 4950 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 4980. It may also be implemented as part of a smartphone 4982, personal digital assistant, or other similar mobile device.

Various implementations of the systems and techniques described hereincan be realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementations in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium” and“computer-readable medium” refer to any apparatus and/or device (e.g.,magnetic discs, optical disks, memory, Programmable Logic Devices(“PLDs”)) used to provide machine instructions and/or data to aprogrammable processor, including a machine-readable medium thatreceives machine instructions as a machine-readable signal. The term“machine-readable signal” refers to any signal used to provide machineinstructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed herein can be implemented on a computer having a displaydevice (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD)monitor) for displaying information to the user and a keyboard and apointing device (e.g., a mouse or a trackball) by which the user canprovide input to the computer. Other kinds of devices can be used toprovide for interaction with a user as well; for example, feedbackprovided to the user can be any form of sensory feedback (e.g., visualfeedback, auditory feedback, or tactile feedback); and input from theuser can be received in any form, including acoustic, speech, or tactileinput.

The systems and techniques described herein can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include aLAN, a WAN, and the Internet.

CONCLUSION

The foregoing description provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

For example, various user devices, ranking systems, and servers havebeen described in the examples above. In some implementations, a userdevice, ranking system, and/or server, of one example, may be the sameuser device, ranking system, and/or server of another example.

Also, example user interfaces have been described. In otherimplementations, the user interfaces may include additional items ofinformation, fewer items of information, different items of information,or differently arranged items of information.

While it has been described that certain data is collected, this datamay be collected while maintaining users' privacy. In other words, thedata may be anonymized with regard to the identities of the usersassociated with the data.

As used herein, the term component is intended to be broadly interpretedto refer to hardware or a combination of hardware and software, such assoftware executed by a processor.

It will be apparent that systems and methods, as described above, may beimplemented in many different forms of software, firmware, and hardwarein the implementations illustrated in the figures. The actual softwarecode or specialized control hardware used to implement these systems andmethods is not limiting of the implementations. Thus, the operation andbehavior of the systems and methods were described without reference tothe specific software code—it being understood that software and controlhardware can be designed to implement the systems and methods based onthe description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of the possible implementations. Infact, many of these features may be combined in ways not specificallyrecited in the claims and/or disclosed in the specification. Althougheach dependent claim listed below may directly depend on only one otherclaim, the disclosure of the possible implementations includes eachdependent claim in combination with every other claim in the claim set.

No element, act, or instruction used in the present application shouldbe construed as critical or essential unless explicitly described assuch. Also, as used herein, the article “a” is intended to include oneor more items and may be used interchangeably with the phrase “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A method implemented by one or more processors,comprising: determining that sound, detected by an electronic device ofa user, includes one or more particular spoken words; selecting, basedon the sound including the one or more particular spoken words, aparticular microsite from a plurality of candidate microsites;identifying a stored network address for the particular microsite;identifying a stored sensor indication for the particular microsite,wherein the stored sensor indication indicates a sensor that is relevantto the particular microsite; obtaining, based on the stored sensorindication indicating the sensor that is relevant to the particularmicrosite, sensor data that is generated based on output from the sensorthat is relevant to the particular microsite; and transmitting, to thestored network address for the particular microsite, a request thatincludes the sensor data, wherein the request includes the sensor databased on the stored sensor indication indicating that the sensor isrelevant to the particular microsite, wherein transmitting the requestcauses microsite content that is based on the sensor data to betransmitted to the electronic device or to an additional electronicdevice.
 2. The method of claim 1, wherein selecting the particularmicrosite is further based on profile data of the user.
 3. The method ofclaim 1, wherein the first sensor data is received independent of inputof the user.
 4. The method of claim 1, wherein the microsite content istransmitted to the electronic device for presentation of the micrositecontent to the user via the electronic device.
 5. The method of claim 4,wherein the electronic device is a watch.
 6. The method of claim 1,wherein the microsite content includes an amount of content that can bepresented on a display of a watch.
 7. The method of claim 1, wherein themicrosite content includes embedded instructions.
 8. A server devicecomprising: memory storing instructions; one or more processors,operatively connected to the memory and executing the instructions tocause the one or more processors to: determine that sound, detected byan electronic device and capturing a voice of a user, satisfies one ormore criteria; select, based on the sound satisfying the one or morecriteria, a particular microsite from a plurality of candidatemicrosites; identifying a stored network address for the particularmicrosite; identifying a stored sensor indication for the particularmicrosite, wherein the stored sensor indication indicates a sensor thatis relevant to the particular microsite; obtaining, based on the storedsensor indication indicating the sensor that is relevant to theparticular microsite, sensor data that is generated based on output fromthe sensor that is relevant to the particular microsite; andtransmitting, to the stored network address for the particularmicrosite, a request that includes the sensor data, wherein the requestincludes the sensor data based on the stored sensor indicationindicating that the sensor is relevant to the particular microsite,wherein transmitting the request causes microsite content that is basedon the sensor data to be transmitted to the electronic device or to anadditional electronic device.
 9. The server device of claim 8, whereinthe one or more criteria comprise that the voice is a particular type ofvoice.
 10. The server device of claim 8, wherein the one or morecriteria comprise that one or more particular words are detected in thesound.
 11. The server device of claim 8, wherein in selecting theparticular microsite, one or more of the processors are further toselect the particular microsite further based on profile data of theuser.
 12. A method implemented by one or more processors, the methodcomprising: receiving user interface input that activates, for a user, aparticular microsite that includes triggering criteria, the triggeringcriteria comprising at least: a geographic location criterion thatdefines that a user is not at a particular geographic location, and asound criterion that defines a particular sound being detected;subsequent to activating the particular microsite for the user:determining occurrence of the triggering criteria for the user and forthe particular microsite, determining the occurrence of the triggeringcriteria including: determining that the user is not at the particulargeographic location, and determining, based on audio data from a givenelectronic device of the user, that the particular sound is detected; inresponse to determining the occurrence of the triggering criteria:causing microsite content, for the particular microsite, to be renderedat an additional client device of the user.
 13. The method of claim 12,wherein detecting the particular sound comprises detecting a humanvoice.
 14. The method of claim 13, wherein detecting the particularsound comprises detecting the human voice above a particular threshold.15. The method of claim 13, wherein detecting the particular soundcomprises detecting that the human voice is a particular type of voice.16. The method of claim 12, wherein the microsite content comprises anaudio clip that includes the audio data from the given electronic deviceof the user.
 17. The method of claim 12, wherein the microsite contentidentifies one or more properties of the audio data, the one or moreproperties of the audio data determined, by the microsite, based onprocessing the audio data.
 18. The method of claim 12, wherein thetriggering criteria further comprise a date criterion that defines aparticular day or particular day of the week.
 19. The method of claim12, wherein the triggering criteria further comprise a time criterionthat defines a time or time range.
 20. The method of claim 12, whereinthe microsite content includes an amount of content that can bepresented on a display of a watch.